Microsoft KB Archive/169218: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
| Line 12: | Line 12: | ||
<div id="TitleRow"> | <div id="TitleRow"> | ||
= <span id="KB169218"></span>FIX: | = <span id="KB169218"></span>FIX: "Invalid Argument Value" Error with SQLSetConnectOption = | ||
| Line 52: | Line 52: | ||
<div class="errormessage"> | <div class="errormessage"> | ||
szSqlState = | szSqlState = "S1009", *pfNativeError = 0, *pcbErrorMsg = 55<br /> | ||
szErrorMsg = | szErrorMsg = "[Microsoft][ODBC Driver Manager] Invalid argument value" | ||
</div> | </div> | ||
Latest revision as of 11:04, 21 July 2020
Article ID: 169218
Article Last Modified on 8/27/1999
APPLIES TO
- Microsoft Open Database Connectivity 3.0
This article was previously published under Q169218
BUG #: 4622 (ODBC30)
SYMPTOMS
When SQL_ODBC_CURSORS is set to SQL_CUR_USE_ODBC using the SQLSetConnectOption and a connection to a data source is made, the next call to SQLSetConnectOption to set the SQL_CURRENT_QUALIFIER or SQL_ATTR_CURRENT_CATALOG fails with the following message:
WORKAROUND
To work around this problem, use SQLSetConnectOption to set the SQL_ODBC_CURSORS to SQL_CUR_USE_IF_NEEDED or SQL_CUR_USE_DRIVER. The ODBC Cursor Library version 3.00.2822 resolves this issue.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Open Database Connectivity version 3.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft Open Database Connectivity, version 3.0. For more information, contact your primary support provider.
MORE INFORMATION
This behavior is only seen with ODBC 2.X applications using a Driver Manager 3.0 and a 2.X ODBC driver.
Additional query words: DM Cursorlibrary
Keywords: kbbug kbfix kbprogramming KB169218
