Microsoft KB Archive/89587

= ACC: DoCmd Statement in Transaction Not Affected by Rollback =

Article ID: 89587

Article Last Modified on 2/12/2007

-

APPLIES TO


 * Microsoft Access 1.0 Standard Edition
 * Microsoft Access 1.1 Standard Edition
 * Microsoft Access 2.0 Standard Edition
 * Microsoft Access 95 Standard Edition
 * Microsoft Access 97 Standard Edition

-



This article was previously published under Q89587



SUMMARY
Advanced: Requires expert coding, interoperability, and multiuser skills.

In Microsoft Access, the DoCmd Object (or the DoCmd statement in version 1.x and 2.0) is not affected by a Rollback statement if the DoCmd Object appears in a transaction.



MORE INFORMATION
Transaction processing in Microsoft Access is valid only on virtual table (VT) objects, such as dynasets. The DoCmd Object starts another Microsoft Jet database engine session to process its arguments.

Because the Jet database engine manages transaction processing, a new session of the Jet database engine contains its own transaction management. The two are mutually exclusive; transactions in one are not managed or affected by transactions in the other.

The simplest workaround for this problem is the QueryDef.Execute method, which uses a recordset.

NOTE: The QueryDef.Execute method works only when a QueryDef action is based on an action query (update, insert, delete) that does not return a recordset.

Additional query words: commit record set

Keywords: kbinfo kbusage KB89587

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.