Friday, July 25, 2008

Error Code 3734

PRB: Error Message 3734 Occurs When You Repeatedly Open and Close MDB File
Q274211. The information in this article applies to:
Microsoft Visual Basic Professional Edition for Windows, version 6.0
Microsoft Visual Basic Enterprise Edition for Windows, version 6.0

SYMPTOMS
If you repeatedly open and close a Microsoft Access database (MDB) in a multiuser situation, the following 3734 run-time error message may occur:
The database has been placed in a state by user ‘Admin’ on machine ‘machinename’ that prevents it from being opened or locked.

CAUSE
Jet locks a block of 256 bits in the MDB header. Included in this block of bits are bits that indicate a “passive shutdown”, which causes the error message described in the “Symptoms” section to occur. You may have users that open and close the MDB file rapidly and the bits are not getting unlocked quickly enough. When a user tries to open the MDB file, if the program is not able to read the bits, Jet assumes that the user is in a “passive shutdown” or “admin mode”, and therefore will not let the user open the MDB file.

RESOLUTION
Repeatedly opening and closing a Microsoft Access database is not recommended. Open the database once at the beginning of the application, and then close the database at the end of the application.

STATUS
This behavior is by design.

MORE INFORMATION
The 3734 error code is new with Microsoft Access 2000. Jet 4.0 introduces a new feature called Connection Control. Error 3734, associated with this feature, normally occurs when you try to open a database if the database is opened exclusively by another user. Databases are opened exclusively when design changes are being made. However, no design changes are being made to the database in this situation when the error occurs.

The Following Comment was left by "Farvish" (Thanks for that)

"Very nice posting. sometime this error may come due to corrupted table or missing refrences. In this situation you can repair it using compact and repair utility or access repair>/a> tools."

No comments: