|
The Express for Windows database may be locked
by a user who
-
has crashed,
-
or, who has done an End Task on Express,
-
or, whose system is awaiting a response to a
prompt such as OK or Continue?
-
or, who has failed to exit open screens within
Express before turning off their system.
Solutions for Network Installations:
-
Make sure that another user does not have an
Express communications session open that is awaiting the response to a
system prompt, such as OK or Continue. This could result in
the Express database being temporarily locked awaiting a response to the
prompt.
-
Check the file attributes of the files
EXPRESS.LDB and EXPRESS.MDB and make sure that neither of the
files has been set to Read-Only status. If so, remove the Read-Only
attribute and try again. If that does not work, go to the next step...
-
Try to determine which user has caused the
problem. Have that user log out and reboot their system. If you are
unable to determine which user has locked the file, have any user who has
accessed the Express program recently log out and reboot.
Solutions for Standalone Installations:
-
Check the file attributes of the files
EXPRESS.LDB and EXPRESS.MDB and make sure that neither of the
files has been set to Read-Only status. If so, remove the Read-Only
attribute and try again.
-
Make sure that the user does not have a
previously opened session of Express still running and minimized. If so,
Express does not need to be relaunched. Use the session that is already
active.
-
If neither of the above appears to be the
answer, simply reboot the system and then try again.
|
