asked on
Red padlock on .ldb file when Access database opened.
I have to convert an old 2000 .mdb database for a customer who has been have issues to a 2016 Access database on a Windows 10 machine and their .ldb file has a red padlock on it every time they open the database .mdb file. What is this and how do I get rid of it?
DatabasesMicrosoft Access
Last Comment
Annmv888
ASKER
Thanks for the information but I've never seen this before and it isn't on any of the other databases I work with. This is the first one so how did it end up on this one and none of the others?
It's not Windows doing that....did you add any 3rd party software recently, such as a VPN service?
In any case, with everyone out of the DB, delete the .LDB file if it is there. If you can't delete, easist thing to do is reboot, then try the delete again.
As Fabrice said, the .LDB is normally there whenever someone is in the database.
Jim.
In any case, with everyone out of the DB, delete the .LDB file if it is there. If you can't delete, easist thing to do is reboot, then try the delete again.
As Fabrice said, the .LDB is normally there whenever someone is in the database.
Jim.
ASKER
The .ldb and .laccdb files are always there but now for this one they have this padlock.
Our company is working from home and we are using Cisco AnyConnect.
Our company is working from home and we are using Cisco AnyConnect.
.. for this one they have this padlock.
They always have this - it is the icon of the lock file (with the previous Access logo, by the way):
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks, it must be something new then with this version. I appreciate all the help and I guess I won't worry about it because that is what I am seeing.
it must be something new then with this version
No. It has been this way since version 1.0.
ASKER
Thanks, it must be something new then with this version. I appreciate all the help and I guess I won't worry about it because that is what I am seeing.
It is part of Access's internal functionalities, and it is a normal behavior.
don't worry about it.