By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,398 Members | 1,301 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,398 IT Pros & Developers. It's quick & easy.

Windows 2000 Server Listed as a User in an Access XP Dabase

P: n/a
Through the LDB viewer we are seeing one of our servers in the "users
listed" list.

The information is legitimate as we have code that is dependent on the
non-presence of the LDB file. The code is failing to execute because
even programmatic access to the MDB file produces the LDB file. While
it is my understanding the accessing the MDB in "exclusive" mode will
not produce the LDB file I am not certain if the developer opens in
"exclusive" mode or simply relies on the absence of the LDB file at
the outset. I am entering this situation as a "maintenance" developer
post downsizing. And you can guess… the primary knowledge holder
is among the "down sized."

It is my impression that programmatic access produces the same result
listed below.

In detail: We start with a single MDB file and no LDB file located on
a "Freshly rebooted" Windows 2K Server. When a single user opens the
MDB we see two "users listed." In the LDB viewer we see the correct
workstation (as expected) and the Windows 2000 Server (not
expected/desired). After the user at the workstation logs off the LDB
remains with one user listed - the Windows 2000 Server. Only after
rebooting can we delete the LDB file.

Note that we have the same "setup" (below) at 5+ other sites. None of
the other sites is exhibiting the same behavior.

Setup: Windows 2000 Server - Access XP Database located on the same

Any ideas/suggestions will be greatly appreciated. Even bad ideas are
worth mulling over for a few moments!
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.