Who's Using My Database?

[WayneRyan]

Hi all,

Have a small problem here. I have a Windows 2000 server
running an Access app. The DB is not split. Access
Security is in place, but doesn't seem to be a problem.
Every once in a while we try to open the DB for maintenance
Access says: "You can't make changes ... the file is in use".

The Windows Admin tools show that there is nobody accessing
that file.

Trying to delete the .ldb returns "The file is in use."

So far, the only solution is to reboot the server and wait
for next time.

Anybody seen this before?

Wayne

 

[ReAn]

Over the last nine years that ive worked with windows i've noticed it has a tendency on occasion to lock files. What i mean is, even though you've re-booted/closed everything and so on, some files cannot be deleted because windows thinks they are in use. I've noticed A similar phenominon (sp?) with access databases in the situation that sometimes windows (access?) likes to leave them locked.

Solution: Select DB, copy/paste, Del old DB, rename new DB to old name.

This sometimes happens to me after compacting. I know that sometimes i had to do this to get my ASP to read my DB's through ADODB sometimes.

Give it a try, see what happens.

 

[ghudson]

You can open the .ldb file in Notepad to see who's PC was in the db when it was locked up. The .ldb file will give you the users workgroup name [if you are using Access security] and also the users Computer Name. You will have to reboot the users PCs that are listed in the .ldb file if everybody is out of the db yet you still can not do what you want.

This is common if the db is shared yet not split. Also, does everybody have the correct permissions to the directory where the db is located for they should be able to create/edit/delete files in that directory.

Search the forum for .ldb and you should find more posts where this topic has been discussed before.

Good luck!

 

[WayneRyan]

ReAn & ghudson,

Thanks for the response. The user/workstation with the .ldb in use
is the Administrator/Server itself. I think that this is a very subtle
Windows/Networking issue.

I've done a google search & this does happen, but haven't seen a
solution.

Thanks for the help!

g, you better get back to Cosmos' SendKeys problem.

Wayne