Locking File Question

[Guest]

With direction from some fine MVPs, I was able to find a program that will
boot users off the database when I need to. For that, I thank you
tremendously. Last Friday however, it keep telling me that others were still
logged into the system. I viewed the locking file and saw that I had a
couple of entries. Since I have not been able to clone myself, I knew I was
NOT on the database. I have done some of the reading here regarding this
subject but have not been able to find a method whereby I could delete this
locking file when I know it is safe. Any Ideas how to accomplish this?

Thank you for your assistance!

 

[Douglas J. Steele]

Realistically, you can't delete it unless it's safe to do so: Windows won't
let you. In other words, if you can delete it, it's safe to.

 

[Guest]

But if I KNOW it is safe but the locking file says no, you're saying I'm
stuck? Is there nothing I can do to gain exclusive access?

 

[Douglas J. Steele]

Doesn't matter what you think, it's what Windows thinks! <g>

Perhaps someone quit the application by quitting Access, as opposed to
getting out of the application properly, or there could be some other reason
why Windows thinks there's still a connected thread. Sometimes it's actually
necessary to reboot the server to correct the problem.

 

[Guest]

Thank you, Doug. I wasn't trying to argue with you; just thought there
should be an easy way but alas. . . Thanks for you assistance! It is
appreciated!

 

[Guest]

Doug,

Just one more question on this subject if I may.

When you are saying quitting Access instead of getting out properly, are you
saying using the 'Big red X' at the upper right hand corner of the screen is
a no-no? Or doing the 'File>Exit' is a no-no. I have been telling people to
use the 'File>exit' method but just want to make certain.

Thank you!

 

[Douglas J. Steele]

The "Big red X" is a common culprit, as is shutting down Windows.