ldb file

R

Reggie

Hi and TIA. I have a backend db on my server. I often want to compact &
repair it, but cannot due to not being able to delete the ldb file. I have
a procedure from my frontend that checks logged on users. It indeed states
that several people are logged on when in fact I know that no one is. Why
is it showing them still logged on and how can I force them out so that I
can compact & repair the backend? I have a procedure that kicks everyone
off, but even running this I run into the same issue. I know I can copy the
backend to a new location, compact & repair, and re-establish the linked
tables, but that doesn't solve, explain or prevent this from happening. Any
advice is appreciated. Thanks for your time.
 
D

Douglas J. Steele

If the application was closed incorrectly (such as just shutting down Access
by clicking on the X in the upper right-hand corner, or shutting down the
workstation, the thread to the database may not have been released.

While a pain, you may have to reboot the server, and thus release all open
connections.
 
R

Reggie

Thanks Doug! Is there a procedure that will force it to shut down when they
click the X or the workstation is closed whilst the app is still open?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top