BUG: Error 206 Calling Procedure with SQL_DEFAULT_PARAM

ID: Q161591

The information in this article applies to:

Microsoft SQL Server version 6.5
Microsoft Open Database Connectivity, version 2.5

BUG #: 16386

SYMPTOMS

If an application specifies SQL_DEFAULT_PARAM for pcbValue when doing a SQLBindParameter on a parameter in a SQL Server stored procedure, and the parameter has a default of NULL, the following SQLExecute or SQLExecDirect will fail with SQL_ERROR, and a call to SQLError will return the following error:

szSqlState = "22005", *pfNativeError = 206,
szErrorMsg="[Microsoft][ODBC SQL Server Driver][SQL Server]
Operand type clash: NNN is incompatible with void type"

where NNN is the datatype of the parameter (for example, int or char).

WORKAROUND

To work around this problem, specify SQL_NULL_DATA instead of SQL_DEFAULT_PARAM for pcbValue.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5 and Open Database Connectivity version 2.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Keywords          : kbinterop kbusage SSrvProg kbbug6.50 
Version           : 6.5 2.5
Platform          : WINDOWS 
Issue type        :

Last Reviewed: April 7, 1999