Phantom DB user (.ldb file)

I'm running a database I created for about 10 people.  At the end of each day, I compact and repair it.  For the last 3 days, there appears someone is locked in the database because I see a .ldb file along with the database file.  This usually indicates someone is in the database but I've had everyone log out and restart their computers and the file is still there.  I can't compact and repair it as long as it thinks someone is logged in it.  

What could be the cause for this?  I've seen this happen a couple times before but it usually takes care of itself within a day or so.  

Is there away to manually disconnect the .ldb file?  I can still back a backup copy of the database.  I've already tried deleting the .ldb and .mde files but it won't let me do this.  The main copy of the database is a .mde format.

Thanks,
David
dddwAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
In this particular situation, are you manually able to delete the LDB file?

Do you have the Compact On Close option set ?

mx
0
dddwAuthor Commented:
No to both questions.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Well, it's pretty unusual that once everyone reboots ... not to have an LDB file cleared out ... assuming it's not just an orphan LDB ... which if it was, you would be able to delete it ... and even without deleting it, C&R would work.

What happens say ... if you have this stuck LDB ... someone opens the mdb normally, then closes normally ... does it then go away?

This is a handy free program which my help (good for many other issues also):

http://ccollomb.free.fr/unlocker/

mx

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

dddwAuthor Commented:
It stays open no matter what.  I've had everyone open and close the database a few times.  Another possibility is that there are Word Mail Merge documents that are linked to queries in this database to merge in data for letters.  It is possible that one of these Word Mail Merge docuemnts is stuck open which would create a .ldb file.  This is not very likely since everyone has rebooted at least one time.

This unlocker program looks interesting.  Perhaps that will work.

I'll give it a try this evening after everyone is out and I've made a backup.  You would think it would have crash by now but it hasn't.  That's a good thing!

David
0
dddwAuthor Commented:
Would I unlock the .ldb or the .mde file or both?
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Unlock the LDB file.  However ... I give this a 50/50 chance of working.

" It is possible that one of these Word Mail Merge docuemnts is stuck open which would create a .ldb file.  "

Unless some automation process is doing this, I don't think so.  

Is this a shared MDB or a split configuration wherein each user has a copy of the Front End on their workstation and is linked to the Back End on a server ?  If not, it should be this way.

mx
0
dddwAuthor Commented:
I've had this database configured as front end and back end and had some slow connection issues with a work at home employee.  Ideally, it should be front end and back end but I ended up using one database on a shared drive saved in a .mde format (everyone accesses it via a shortcut).  This is why it is compacted and repaired daily because it is prone to have problems in this configuration.  Periodically, I make a new database and only import the main table from the "service" database to be sure it stays corruption free.  

This has worked well for more than a year.  I'm sure there are better ways to design it but this was the best I could do with no I.T. help.  Another issue in the design of this database is that it is designed to do letter generations with Word Mail Merge.  I have a lot of memo fields in the tables to accommodate the language that goes in the letters.  These memo fields can make it prone to corruption.  

Not ideal but the best I could do and it has worked for sometime now.  Perhaps my luck is running out...
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Still ... not seeing how any of that per se would result in a stuck LDB.

mx
0
dddwAuthor Commented:
I'll let you know if it unlocks.  Thanks.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
ok ...
0
dddwAuthor Commented:
The evening I was going to use the unlocker the .ldb file went away on its own.  I have the unlocker software now in case it happens again.  Thanks for the help.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
lol.  Maybe it saw the unlocker and got scared !!

mx
0
dddwAuthor Commented:
I thought the same thing!
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Hey ... that Unlocker is very cool and simple. Works good for example ... were your try to eject a USB flash drive ... and Windows says it's 'BUSY'.  No problem ... unlocker kills it.

mx
0
Thatsmej1Commented:
Try to determine who the owner of the file is.

Right click it and then go to Security -> Advanced -> Owner.

If the user is different from yourname. Check if that other user has an connection to the MDB.

If its on an network drive. You can check who has an open session to the file.
You can do this, by logging in on the server and to the following:
Right Click on My computer -> Manage
On the left side you have an option sessions / shares etc.
Check out the sessions.
If any one has still an open session, check that users Task Manager for MSaccess.exe processes.
0
dddwAuthor Commented:
Thanks for the tip.  I did check the file as you suggested "Security -> Advanced -> Owner" and it showed a user's name but I confirmed she had logged out of the db and restarted her computer.  The db is on a network and I have restricted access to the shared drive so I can't do the 2nd suggestion.  

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.