R
RLM
Through the Access LDB viewer (MS tool used to "see" who is using an Access
database) we are seeing one of our Windows 2000 servers as a "listed user."
For those that do not know: A "LDB" is a file created by MS Access when 1 or
more users open an Access database in "non-exclusive" mode. The "LDB" file
exists for the duration of database sessions. During session time the "LDB"
file cannot be removed.
In detail: We start with a single database file (.mdb) and no LDB file
located on a "Freshly rebooted" Windows 2K Server. When a single user opens
the Access database from a workstation we see two "users listed." In the LDB
viewer we see the workstation (as expected) and the Windows 2000 Server (not
expected/desired). After the user at the workstation logs off we still see
the Windows 2000 Server as a listed user.
Only after rebooting can we delete the LDB (lock) file. Which translates to
the fact that "Access" is behaving as if the Windows 2000 server is using
the database file.
Note that we have the same "setup" (below) at 5+ other sites. None of the
other sites are exhibiting the same behavior.
Setup: Windows 2000 Server - Access XP Database located on the server.
Any ideas/suggestions will be greatly appreciated. Even bad ideas are worth
mulling over for a few moments!
database) we are seeing one of our Windows 2000 servers as a "listed user."
For those that do not know: A "LDB" is a file created by MS Access when 1 or
more users open an Access database in "non-exclusive" mode. The "LDB" file
exists for the duration of database sessions. During session time the "LDB"
file cannot be removed.
In detail: We start with a single database file (.mdb) and no LDB file
located on a "Freshly rebooted" Windows 2K Server. When a single user opens
the Access database from a workstation we see two "users listed." In the LDB
viewer we see the workstation (as expected) and the Windows 2000 Server (not
expected/desired). After the user at the workstation logs off we still see
the Windows 2000 Server as a listed user.
Only after rebooting can we delete the LDB (lock) file. Which translates to
the fact that "Access" is behaving as if the Windows 2000 server is using
the database file.
Note that we have the same "setup" (below) at 5+ other sites. None of the
other sites are exhibiting the same behavior.
Setup: Windows 2000 Server - Access XP Database located on the server.
Any ideas/suggestions will be greatly appreciated. Even bad ideas are worth
mulling over for a few moments!