Solved Access 2000 - Database Locked when opened by a specific computer.

askavatar

New member
Local time
10:15 PM
Messages
23
Hi again, everyone. I'm having some Access woes with which I have been unable to find help about around the web, as my circumstances don't seem to fit other reports of this problem. I get the dreaded:
The database has been placd in a state by user <name> on machine <name> that prevents it from being opened or locked.


Here's the kicker, its used actively by 2 users, when user 1 opens it, user 2 gets that error (or any other person that tries to get into the database), if user 2 opens it first (or any other user) then any and all users that open it up can use it without any problems.

Now, I don't have any plugins in use, no VB code getting data from other sources, or mail merges, or anything like that, everything in this database is internal. What I can't figure out is ONLY user 1's computer will lock the database and ONLY when she's the first to open it.

Any Ideas?
Avatar
 

My Computer

Computer Manufacturer/Model Number
Custom
OS
Windows 10 Professional x64
CPU
Intel Core i5-4690K Devil's Canyon Quad-Core 3.5GHz
Motherboard
Gigabyte GA-Z97MX Gaming 5 (Rev. 1.0)
Memory
G.Skill AEGIS 16GB PC3-12800
Graphics Card(s)
Sapphire Dual-X Radeon R9 280
Sound Card
Integrated Motherboard Sound
Monitor(s) Displays
42" Insignia LCD TV
Screen Resolution
1920x1080
Hard Drives
System: Kingston SSDNow M.2 SATA
Internal 1: Western Digital 7200RPM 2TB SATA III
External 1: Western Digital 7200RPM 3TB USB 3.0
PSU
Rosewill Bronze RBR1000-M 1000W w/Modular Cabling
Case
Antec 900 Series
Keyboard
Logitech K350
Mouse
Logitech M510
Internet Speed
100 MBPs
See if there is a left-over <name>.ldb file in the same directory as the <name>.mdb file. the LDB file (Lock Data Base) is where Access keeps track of who has the file open, which record is being accessed, etc. The LDB file is supposed to get deleted with the database is closed, but if there is a crash or something weird then LDB file can get left behind.

If you find an LDB file just delete it and try again.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom built
OS
Win7-64
CPU
Intel i7-3770S
Motherboard
ASUS P8Z77-M
Memory
16GB
Graphics Card(s)
nVidia GT630
Sound Card
onboard
Monitor(s) Displays
dual
Screen Resolution
1920x1200 (primary) 1050x1680 (secondary)
Hard Drives
128GB SSD (boot)
64GB SSD (Temp/My Documents)
500GB (photos/videos)
1TB (rendered video, backups)
PSU
650W
Case
Thermaltake A30
Cooling
Thermaltake
Keyboard
Logitech Lighted
Mouse
Kensington Expert Mouse (trackball)
Internet Speed
FIOS 35/35
Antivirus
MS Security Essentials
Browser
Chrome (beta)
Well, I just got done writing a front end for it, and creating a duplicating program that I ran across over on the dbforums.

To answer your question bbinnard, there were no errant LDBs, this has been an ongoing thing with this database. I just thought it was strange that it was always the same computer having the problem. Making up the frontend didn't take as long as I thought it would.
 

My Computer

Computer Manufacturer/Model Number
Custom
OS
Windows 10 Professional x64
CPU
Intel Core i5-4690K Devil's Canyon Quad-Core 3.5GHz
Motherboard
Gigabyte GA-Z97MX Gaming 5 (Rev. 1.0)
Memory
G.Skill AEGIS 16GB PC3-12800
Graphics Card(s)
Sapphire Dual-X Radeon R9 280
Sound Card
Integrated Motherboard Sound
Monitor(s) Displays
42" Insignia LCD TV
Screen Resolution
1920x1080
Hard Drives
System: Kingston SSDNow M.2 SATA
Internal 1: Western Digital 7200RPM 2TB SATA III
External 1: Western Digital 7200RPM 3TB USB 3.0
PSU
Rosewill Bronze RBR1000-M 1000W w/Modular Cabling
Case
Antec 900 Series
Keyboard
Logitech K350
Mouse
Logitech M510
Internet Speed
100 MBPs
Back
Top