PRB: Jet 3.0 UserCommitSync & ImplicitCommitSync Values Wrong

 Last reviewed: July 31, 1997
Article ID: Q153491
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2

SYMPTOMS

If you explicitly specify values for the Jet 3.0 UserCommitSync or ImplicitCommitSync keys in the registry, these values will not have the expected effect.

CAUSE

According to the Microsoft Jet Database Engine Programmer's Guide, the UserCommitSync and ImplicitCommitSync keys can have the following values:

"Yes signifies that Microsoft Jet will wait for commits to finish. Any other value means that Microsoft Jet will perform commits asynchronously."

Jet 3.0 incorrectly interprets the value "yes" as asynchronous and "no" as synchronous for these two keys.

RESOLUTION

Specify "yes" for asynchronous and "no" for synchronous.

STATUS

We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

These string values can be explicitly set in the registry under:

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\3.0\Engines\Jet

REFERENCES

Microsoft Jet Database Engine Programmer's Guide. 

Keywords          : MfcDAO MfcDatabase kbenv
Technology        : kbMfc
Version           : 4.0 4.1 4.2
Platform          : NT WINDOWS
Issue type        : kbprb

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

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