Difference between revisions of "Microsoft KB Archive/169469"
(importing KB archive)
m (Text replacement - """ to """)
|Line 62:||Line 62:|
*szSqlState = S1000, *pfNativeError = -1103,<br />
*szErrorMsg = [Microsoft][ODBC Microsoft Access 97 Driver]
|Line 69:||Line 69:|
szSqlState = S1000, *pfNativeError = -1103, *pcbErrorMsg = 110<br />
szErrorMsg=[Microsoft][ODBC Microsoft Access 97 Driver] Couldn't start transaction; too many transactions already nested.
Latest revision as of 11:04, 21 July 2020
Article ID: 169469
Article Last Modified on 2/12/2007
- Microsoft Open Database Connectivity 2.5
- Microsoft Open Database Connectivity 3.0
- Microsoft Access 97 Standard Edition
This article was previously published under Q169469
BUG #: 4841 (Brazos)
If an application does the following in the Microsoft Access 7.0 or 97 version of the ODBC drivers more than seven times
SQLSetConnectOption(hdbc, SQL_AUTOCOMMIT, SQL_AUTOCOMMIT_OFF);
SQLTransact(henv, hdbc, SQL_COMMIT);
The error generated is:
If the application calls SQLExecDirect with any SQL statement, the error generated is:
To work around this problem, do not set the SQL_AUTOCOMMIT option repeatedly within a connection. The SQL_AUTOCOMMIT option is a per-connection option. Once this option is set, it stays valid until the connection is dropped; an ODBC application does not have to set the option repeatedly within a connection.
Microsoft has confirmed this to be a problem in the Microsoft Access ODBC driver version 3.50.3602. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: SQLEndTran SQLSetConnectAttr
Keywords: kbbug kbprogramming KB169469