MDB file not open, but LDB file exists anyway

[James Benton]

Group,

I am running NT server with 15 users. I have a FE database in a hidden
folder. When the user logs on to the network a batch file copies this MDB
file to the local machine and the user uses the local copy to get to the
data. Lately though, if I try to open the server copy of the MDB file to
make little tweaks to it, I dont' have exclusive access and there is the
corresponding LDB file perched next to it.

I'm stuck. Any idea what might be going on? I have even gone so far as to
turn off 14 machines altogether. No difference.

Thanks in advance

Jim Benton

[Stephany Young]

As long as you are absolutely sure that noone has the database open then
delete the .ldb file.

They can get left behind when a user has an 'unclean' exit from access.

"James Benton" <Pla...@WhereTheMonkeyDropsIt.com> wrote in message
news:Jrb56.2193$jO.1...@bgtnsc06-news.ops.worldnet.att.net...

[Deanna Byrne DPSI Techncial Support]

FYI. You can open the existing LDB through Notepad and see who the system
thinks is still logged into the program. It will tell you the computer name
and the logon name they used to get into the program.

I have clients who track this info and report it to their IT people so they
can investigate network connections, etc.. as the cause.

"Stephany Young" <step...@sysoft.co.nz> wrote in message
news:#$9$QNtdAHA.1796@tkmsftngp03...

[James Benton]

Deanna,

Thank you for the tip. Just dropping the LDB file onto an open notepad
session tells me exactly what I need to know. Sometimes it's the simple
things . . .

Deanna Byrne DPSI Techncial Support <deanna...@dpsi-cmms.com> wrote in
message news:u35OF0wdAHA.2056@tkmsftngp03...

[Tony Toews]

"Deanna Byrne DPSI Techncial Support" <deanna...@dpsi-cmms.com>

wrote:

>FYI. You can open the existing LDB through Notepad and see who the system
>thinks is still logged into the program. It will tell you the computer name
>and the logon name they used to get into the program.

This will tell you who has been logged into the MDB since the last
time it was deleted. And not who is currently logged in. Users who
have exited cleanly will still appear in the LDB file.

Tony
----
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Frank Konzal]

Do you have erase rights the the directory?

[Fred Colman]

Hi,
I've read this thread with great interest because I am having a similar
problem. It's a file server set up with 20 users. Access 2000. No one
is currently running access. Yet there is a ldb file associated with
the tables mdb and another with one of the forms mdb. I cannot erase
either of them - I get a sharing violation. I have administrator
privileges. I cannot read them with notepad as was suggested - it looks
like a binary file. This situation was caused when one of the users
logged in using Terminal Server, and terminal server timed out and
disconnected. This same user logged in again and started Access and
logged out again. The ldb files remain. Worse still is that since this
happened, loading forms is now taking over a minute.
How do I get rid of the ldb files and why are the forms taking so long
to open. Thanks for any suggestions.
Fred

[Tony Toews]

Fred Colman <fr...@reddelicious.com> wrote:

>I've read this thread with great interest because I am having a similar
>problem. It's a file server set up with 20 users. Access 2000. No one
>is currently running access. Yet there is a ldb file associated with
>the tables mdb and another with one of the forms mdb. I cannot erase
>either of them - I get a sharing violation.

Can you log onto the server and see if anyone is using the files?
Has the server been rebooted?

>I have administrator privileges.

But to that particular directory? Including delete rights?