INF: Checking for an ODBC Driver's Transaction Support

 Last reviewed: September 9, 1996
Article ID: Q115813
The information in this article applies to: 

  - Microsoft Open Database Connectivity, version 1.5
  - Microsoft Open Database Connectivity, version 2.0

SUMMARY

The appropriate way to check for a driver's support for transactions is to check the return value from the call to SQLGetInfo with fSQLType=SQL_TXN_CAPABLE. Relying upon SQLTransact with fType=SQL_ROLLBACK to return SQL_ERROR to check the transaction support in not recommended and can lead to unexpected results.

MORE INFORMATION

With ODBC Driver Manager (ODBC.DLL) version 1.5 and later, in case of drivers that export SQLTransact function, SQLTransact with fType=SQL_ROLLBACK will return SQL_SUCCESS. However, the actual driver may not support transactions. SQLGetInfo with fSQLType=SQL_TXN_CAPABLE with return correct information that the driver does not support transactions. This is applicable in general to drivers that support multiple DBMSs.

For example, Database Desktop Drivers fall into the category where SQLTransact is exported, and hence, SQLTransact with fType=SQL_ROLLBACK will return SQL_SUCCESS, though the drivers do not support the transactions. Calling SQLGetInfo with fSQLType=SQL_TXN_CAPABLE correctly return 0 to indicate that the transactions are not supported.

KBCategory: kbusage
KBSubcategory:

Additional reference words: 1.50 Driver Manager VB Visual Basic
Access ODBC Paradox Text Excel Btrieve Foxpro dBase Simba



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.