ACC97: CommitTrans Help Topic Uses dbFlushOSCacheWrites Constant

 Last reviewed: August 29, 1997
Article ID: Q165829
The information in this article applies to:
  • Microsoft Access 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

The Microsoft Access 97 Help topic "BeginTrans, CommitTrans, Rollback Methods" contains the following statements.

In the Syntax section: 

   workspace.BeginTrans|CommitTrans[dbFlushOSCacheWrites]|Rollback
In the third paragraph of the Remarks section: 

   In a Microsoft Jet workspace, you can include the dbFlushOSCacheWrites
   constant with CommitTrans. This forces the database engine to
   immediately flush all updates to disk, instead of caching them
   temporarily.
These statements are incorrect.

RESOLUTION

The dbFlushOSCacheWrites constant was changed to dbForceOSFlush in Microsoft Access 97. Use the dbForceOSFlush constant or its numeric value, which is 1.

MORE INFORMATION

The dbForceOSFlush constant only works if your database resides on a Microsoft Windows 95 or Windows NT computer. If the database file resides on another type of server, such as Novell Netware or Banyan Vines, dbForceOSFlush does not correctly command the operating system to flush all updates to disk. 

Keywords          : DcmHlp kbprg SynFnc
Version           : 97
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbprb
Solution Type     : Info_Provided

================================================================================

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