Repairing Database all the &%$# Time

[Dbless]

I'm running Access 97' the database is about 300 meg. Over the last several days I have to repair the database multiple times a day. Some time the first repair doesn't work and about 30 minutes later I have to repair it again.

Repairing it is easy, I want to find out why and fix the real problem. The only message I get is that when I hope the database "Database needs repaired..."

Any help will do.

 

[KK1967]

have you ever compacted the database? I had the same problem a while back. I upgraded my pc to Office XP and did a compact and repair once or twice and never had the problem again. I may have just been a fluke but an idea

 

[Dbless]

I compact the database every morning because of it's size.

 

[Golom]

Another thing to check is the space availability on the harddrive. I had a 180 MB database on a drive that said it had 120 MB left. Lost whole bunches of data / repaired / compacted all the time, etc. After we moved it to a bigger drive with lots of space all the problems went away.

 

[psemianonymous]

It's possible that something has corrupted, and repairing the database doesn't solve the source of corruption. The big killers are:
--network flux (someone sneezing on your cables)
--too many users (someone sneezing on your file server)
--corrupt MDB (someone sneezed on the MDB itself)


Check the FAQ linked to below--it's a great resource for this sort of thing, and it has a bunch of different fixes you can try.

 

[psemianonymous]

Ack! I uncheck the "signature" by default now, so you might have noticed there is no link. HERE is my signature (and the link I mentioned):

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[Dbless]

The NT server that I'm using has over 6 gb available on the spindal.

Nice thought, but no cigar.

 

[GDGarth]

Is you database split (Front end on local computer, back end on network)? If not, that can cause this problem.

Check to make sure that all of your forms close before you close the database. On one of mine, I had to save the record, close the form, then reopen it every time to prevent corruption.

 

[LogicalmanUS]

dbless,

300 MB is rather a large size, even for Access.

Following GDGarth's excellent advice, and then ensuring the files are compacted (KK1967), and all debug print statements are REMmed out, if the size is still substantial, then I would suggest splitting the database into separate components of logical table groups.

Logicalman