Article ID: 177138 - View products that this article applies to.
This article was previously published under Q177138
Neither Open Database Connectivity (ODBC), nor Microsoft OLE DB Provider, supports Nested Transactions. ActiveX Data Objects (ADO) supports the feature, but only if the underlying provider exposes it. Currently only the Jet OLE DB provider supports Nested Transactions.
Neither ODBC, nor any released OLE DB Provider, exposes Nested Transaction functionality, even if the back-end data source supports this feature.
Nested Transactions are a feature of the Jet engine, but only when accessing the Jet engine directly via Data Access Objects (DAO). If using DAO against a Microsoft database (MDB) file that has an attached ODBC Data Source, any attempt to use nested transactions is ignored.
The ADO Help indicates that ADO supports nested transactions but only if the underlying OLE DB Provider supports nested transactions. The following Microsoft Providers do not support Nested Transactions: OLE DB Provider for ODBC Drivers
Index Server Provider for OLE DB
Active Directory Provider for OLE DB
Sample CodeBelow is the error message and the code snippet that generates the error for ADO when the underlying provider does not support nested transactions:
Here is the code used to generate the error:
Run-time error '-2147168237 (8004d013)':
Only one transaction can be active on this session.
http://msdn.microsoft.com/en-us/data/aa937729.aspxThe Microsoft Jet Database Engine Programmer's Guide (Second Edition), page 425 - "Nesting of transactions", MS Press.
Article ID: 177138 - Last Review: December 5, 2003 - Revision: 4.2