PRB: QueryDef dbFailOnError Doesn't Rollback on Failure

 Last reviewed: May 8, 1997
Article ID: Q168209
The information in this article applies to:
  • Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

Changes made to the database are not rolled back when an Execute operation fails, even when using the dbFailOnError option. The dbFailonError, when used with the Execute method, would roll back any updates if an error occurred. With the QueryDef.Execute method, this is no longer true.

CAUSE

Because using the Execute method with dbFailOnError does not do an implicit transaction, changes made to a database will not be rolled back when it encounters an error.

RESOLUTION

The fastest way to do a bulk query is without an implicit transaction and by explicitly calling BeginTrans/CommitTrans.

STATUS

This behavior is by design.

MORE INFORMATION

In previous releases of Data Access Objects (DAO), if you executed SQL statements they were internally treated as transactions. If you executed a statement with the dbFailOnError flag on and the query failed, the operation was rolled back. For performance reasons, an SQL statement is no longer treated as a transaction. Therefore, if an SQL query fails in Microsoft Access, an incomplete operation may occur. If you think an error may occur, you should explicitly use the statement within a transaction by using the BeginTrans method and the CommitTrans method. However, note that explicit transactions may slow query performance.

Keywords : vb5all VBKBDAO kbprb
Version : 5.0
Platform : WINDOWS

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: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.