Unable to compact and repair Access 2003

The DB has eaten on of my patients... She's in there but I can't find her.  So I tried to compact and repair but it says I have the DB opened but I don't.  I've even logged off and it still won't let me compact and repair.   If I could compact and repair I might find my patient.
Angelia1Asked:
Who is Participating?
 
rspahitzCommented:
On the local copy that you C/R'd can you add the patient back? If not there's probably something going on in your DB that needs to be reviewed (a rule of some sort that is holding on to that existing patient but hiding it from you.  Depending on how large the DB is, it may take a while to dig through and find that rule. It could be a table rule (no duplicate) combined with a rule to hide records marked a certain way (like those with an Active field set to false).  Without seeing the DB, it's hard to tell, and it sounds like there may be some privacy issues (and maybe file size issues) preventing you from attaching it.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
What time is dinner ?

Are you the only one that uses the db ?

"I've even logged off "
Have you rebooted ?

Open Windows Task Manager>>Process ... be sure MSACCESS.EXE is not stuck.

mx
0
 
rspahitzCommented:
I've found that sometimes things get locked and don't automatically get unlocked.
* Locate the directory/folder where you have your database.
* If the DB is open, you will probably see another file with the same name but an different extension (.laccdb or .ldb) which is probably very small in size (a few K or less)
* Make sure the DB is closed (nobody is logged into it)
* delete the .laccdb file
* re-open the DB and try to compact
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Angelia1Author Commented:
Dinner?  Dinner also know as Supper is at 6:00 do you need the address?

No I am not the only one who uses this db but I've turned off all the PCs.  And rebooted mine to try and compact and repair.  

This is a front end back end and the back end is on a server.

I pulled a copy over to my desk top and was able to C/R there but my patient is still missing from view.  However she is in there because it won't let me re-enter her.  Because It will duplicate the record that's how I know she's in there somewhere.

That's probably another question "How do I find my patient"

Still can't C/R over on the server.  They were having issues w the server yesterday.
0
 
Angelia1Author Commented:
there is an ".ldb" file but outside of the front end and back end that's all I see.
0
 
Angelia1Author Commented:
Nothing in the Task Mgr
0
 
rspahitzCommented:
>there is an ".ldb" file but outside of the front end and back end that's all I see.
If the DB is closed, that file should either be deleted or have a size of zero.  Anything else means that it never released the locks and is probably preventing it from getting compacted.  I think you can open it in notepad to see what's in it, but the info will probably not be useful.
If the DB is truly closed, it's safe to delete that file.
0
 
Angelia1Author Commented:
Now another patient isn't showing up
0
 
Angelia1Author Commented:
size of .ldb is 1kb
0
 
rspahitzCommented:
Definitely keep the backup since something odd is going on.  You may be able to re-construct things (not an easy task) if things go badly with the DB.

>size of .ldb is 1kb
Yes, go ahead and  close the DB and delete that file.
0
 
Angelia1Author Commented:
I have a copy of that back end on my desk top
0
 
EirmanChief Operations ManagerCommented:
If your DB becomes corrupted sometimes you can only repair it by re-creating it.
Create a blank db.
Import all your forms / queries / reports / modules into the new database and re-link if necessary
The whole operation might take 10-15 minutes the first time you do it. With practice < 5 minutes.

However, before you do the above you should decompile it as described in the attachment.
(That alone might fix it, if you have been doing a lot of coding).
--DECOMPILE-DB.txt
0
 
Kelvin SparksCommented:
If the backend is on the server, can you arrange a reboot of the server, then delete the ldb file. Or you need someone with administrative rights to delete the ldb.

It is unlikely that the CR will resolve the problem.

Would I be correct in assuming that the way of locating the patients uses a query. It is likely that one side of the query has somehow "lost" as record (Or perhaps never had it) and that the inner join then results in that patient not appearing.

You'll need access to all the tables and to do some detective work to locate this.


Kelvin
0
 
Angelia1Author Commented:
walking away for a minute to clear my head
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Supper ... got it :-)
(kind of early however)
Address ... depends on what State you are in :-)

"size of .ldb is 1kb"
"Server issues"
Got it.
Clearly ... some process on the Server is keeping Access from killing the LDB file.
I assume you cannot delete the LDB on the Server ?
Any chance your Server (share drive) resides on NetApp - a question for IT ?

"Now another patient isn't showing up"
How are you trying to find the patients?  Are you doing this via the front end UI or looking directly in the back end ?
As to why you cannot find these people ... it's possible they were abducted ... by binary Aliens ... hey, it could happen.
0
 
Angelia1Author Commented:
OK
I lost the Key in the main table.
I changed Index to Yes (no duplicates)
added the key back to Social
Went back in and had to re-add my patients.  
There was a server issue yesterday that could be part of it and we have one person who has Access 2013 (the rest have 2003) that always seems to be a thing
but it's working now...  THANK ALL OF YOU

ps It's not a European Supper it's a Southern Supper (we eat Breakfast, Lunch, and Supper)
0
 
rspahitzCommented:
So you think it was a version incompatibility issue? That's certainly possible...may require some Microsoft updates to fix minor issues with respect to that.  Are both patients now appearing? Are you able to handle the C/R?
(I hope your DB doesn't eat any more patients...)
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
So ... down South then ... I would say to a date: "I'm taking you out to Supper" ?
Really ?
0
 
Angelia1Author Commented:
Exactly
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
LOL ...  She would laugh at me in LA !
0
 
alanccwCommented:
You may try third-party tools such as

DataNumen Access Repair

at

http://www.datanumen.com/access-repair/

to scan and repair your Access 2003 database.
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Sooo ... what was the actual solution ?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.