Article ID: 225985 - Last Review: June 28, 2004 - Revision: 2.0 ACC2000: Other Instances of Access Hang When One User Has a Table LockedThis article was previously published under Q225985 This article applies only to a Microsoft Access database (.mdb).
Novice: Requires knowledge of the user interface on single-user computers. On This PageSYMPTOMS
When you try to update data in a table, at some point, Microsoft Access seems not to be responding. The progress bar in Access seems to have stopped advancing, and the pointer becomes an hourglass that persists indefinitely.
CAUSE
A pre-existing transaction has not been committed or has not been rolled back.
RESOLUTION
Commit or roll back any open transactions before processing new transactions.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
When a database is opened by more than one instance of Access, and a table is locked because of some action, such as editing records in Datasheet view or running an action query against a particular table, other instances of Access may stop responding or may appear to have crashed if there is an attempt to modify records within the same, currently locked, table. This behavior may occur with a shared Access database, such as a database shared on a network. CAUTION: If you follow the steps in this example, you modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and follow these steps on a copy of the database. Steps to Reproduce Behavior
| Article Translations
|
Back to the top
