BUG: SQL Server SQLSetParam Fails on the 252nd ParameterLast reviewed: September 9, 1996Article ID: Q111723 |
The information in this article applies to:
BUG# ODBCSS: 2816 (1.01.2920)
SYMPTOMSThe ODBC SQL Server driver returns an error with SQLSTATE S1093 when SQLSetParam is called for the 252nd time on a prepared statement with more than 252 parameter markers in it. Because of this, users of Microsoft Access version 1.1 may see an error,
ODBC Call Failedwhen they try and update an attached table with more than 125 columns.
STATUSMicrosoft has confirmed this to be a problem in ODBC SQL Server Driver version 1.01.2920. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce ProblemFor an ODBC application writer, do the following:
//create a table with 127 columnsCREATE TABLE lot_of_columns (col1 INT, col2 INT, ..., col127 INT)
//Prepare an update statement with 254 parameter markersSQLPrepare: UPDATE lot_of_columns SET col1 = ?,..., col127 = ? WHERE col1 = ?,..., col127 = ?SQLSetParam for each one of these parameters. The 252nd SQLSetParam returns SQL_ERROR: SQLSTATE S1093, [Microsoft][ODBC SQL Server Driver]Invalid Parameter number For users of Microsoft Access version 1.1, do the following:
ODBC - Call Failed. [Microsoft][ODBC SQL Server Driver]Invalid Parameter number |
KBCategory: kbusage
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |