J
Jerry
I built an Access database for a customer that uses MS
Windows 2000 Advanced Server. Several users are able to
open the database from a remote location using Remote
Desktop. However, at times a user is unable to open the
Access file, receiving an error message that the database
has been placed in a state by user Admin. When I view the
Manage My Computer, Shared Folders, Open files, the .ldb
file that opens when a user opens the .mdb file shows a
large number of locks. When this user closes the .mdb
file, the .ldb file also closes, but when they re-open
it, the .ldb # of locks continues to increase. At some
point, other users are unable to open the .mdb file. If I
intervene and close the open .ldb file with the large
number of locks, it allows other users to open the .mdb
file. Is there a way to avoid this intervention? Can you
explain what is happening with these large number of
locks?
Windows 2000 Advanced Server. Several users are able to
open the database from a remote location using Remote
Desktop. However, at times a user is unable to open the
Access file, receiving an error message that the database
has been placed in a state by user Admin. When I view the
Manage My Computer, Shared Folders, Open files, the .ldb
file that opens when a user opens the .mdb file shows a
large number of locks. When this user closes the .mdb
file, the .ldb file also closes, but when they re-open
it, the .ldb # of locks continues to increase. At some
point, other users are unable to open the .mdb file. If I
intervene and close the open .ldb file with the large
number of locks, it allows other users to open the .mdb
file. Is there a way to avoid this intervention? Can you
explain what is happening with these large number of
locks?