We have an Access 2002 db that seems to be corrupted. The end-user has it stored on his C:\ instead of a network drive. We believe the source of corruption may be repeated end-user error (ok he admitted it) by ctrl+alt+del when it moved "too slow" - ldb files were created which could not be deleted via Windows or DOS - was able to delete by starting PC in safe mode. Still cannot open (this is a db that an MD maintains of all hospital policies) - error states it is in use and indicates the MDs PC (shut down doesn't work) - does anyone have any tricks to try to restore. This db is linked to a program which converts Word docs to html files, stores them in the db, and then ??(out of my scope of knowledge) imports them to a network program that all employees can access to review policies. I could have that process backwards. The programmer who wrote the db and administrator program doesn't have any other suggestions other than to call Microsoft and the MD doesn't have $$ in his budget. Any assistance greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Locked Access Db
- Thread starter jaegca
- Start date
I have encountered this type of error and normally rebooting the users pc will allow you delete the ldb files. If that doesn't work then have you tried creating a blank database and importing all the objects from the corrupt database.
Failing that there are some free utilities available that you can find on the net for recovering corrupt files.
Failing that there are some free utilities available that you can find on the net for recovering corrupt files.
There used to be a problem with '97 where if it got corrupted, a ghost db would be created preventing you to get into the actual db. I haven't seen this with 2002 but then again I haven't done alot of network work with '02.
The "ghost" was named something like "yourDBname0.mdb"
where yourDBname.mdb was the actual name. And it was always in the same directory as the real DB.
Memory is a little rusty, but as a rule just make sure there are no other .ldb or .mdb files in the same directory as the good db.
HTH
The "ghost" was named something like "yourDBname0.mdb"
where yourDBname.mdb was the actual name. And it was always in the same directory as the real DB.
Memory is a little rusty, but as a rule just make sure there are no other .ldb or .mdb files in the same directory as the good db.
HTH
- Status
Similar threads
- Locked
- Question
- Question