LOCKED IDB

[Akrt48]

Can anyone tell me what causes a database to have a locked .idb file, even
though everyone has gotten off. We have just had this start happening
occasionally and it creates real havoc when we want to compact and repair or
fix a report etc... It will show someone as being on even though they are
clearly not. I have even gone so far as to shut off the offending computer
to no avail. Thanks

 

['69 Camaro]

Ensure that the database is split, and that all users have "Full Control"
Windows security permissions on the directory where the back end is located
and on the directory on each user's workstation where the front end is
located.

I have even gone so far as to shut off the offending computer
to no avail.

Shutting off a computer doesn't fix the lack of permission to delete the LDB
file upon exiting the database.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.

 

[Larry Daugherty]

The persisting LDB file is often caused by dumping the power on the
offending computer while Access is still open. Another cause is a
flaky Network Interface Card.

HTH

 

[Akrt48]

Thanks everyone, I will look at their permissions! All of you had the same
consensus.