Daily Corruption of Database Index

[Garridon]

I have a database that corrupts nearly every day. I routinely go in and run Compact and Repair--sometimes this works, but I usually have to export the back end into a new database to fix.

What it does: It does a whole bunch of strange things. It doesn't add records--they simply vanish. When it archives, it deletes the record from the current table but doesn't append it to the archive table. This last time, it deleted the contents of one field in two records--but nowhere else. When I had a many-to-many relationship (now removed), it was adding extra records! The most common thing that pops up is a message box indicating that it can't add the record because it would create duplicate values or can't go to the end of the specified record.

I have completely rebuilt the tables from scratch in a new database, rebuilt the queries from scratch, rebuilt the forms from scratch--and none of it has worked. Does anyone have any other ideas?
Linda Adams
Linda Adams/Emory Hackman Official Web site

http://www.hackman-adams.com

Official web site for actor David Hedison:

http://www.david-hedison.com

 

[DougP]

You MUST do this ASAP
create an MDE. here are two FAQ's I wrote to explain it all.

What is an .MDE and why do I need it?
faq181-91

How do I make an .MDE file
faq181-90
DougP, MCP

 

[Rhonin]

One Q's:
Do you have validated fields in your tables?

We have an old LIMS style db that was suffering from this. It turned out to be a number of discrepant entries that violated the validations but for some reason access allowed entry.
Rep and Comp or rebuild would work for awhile until the bad entries would recorrupt the index.

You can try an MDE, personally I seldom use them, but you might try this first.

Luck!

Rhonin
"too many questions, too little time..."

 

[Garridon]

Unfortunately, converting the front end to an MDE file did not resolve the corruption. It corrupted again today, and I had to import the backend into a new database to resolve it. I was really hoping this would finally fix the problems ...

We are on Win2K and Office XP. The corruption problem did exist before we migrated, but it has gotten worse since we did. Could this be causing it?

Linda Adams
Linda Adams/Emory Hackman Official Web site

http://www.hackman-adams.com

Official web site for actor David Hedison:

http://www.david-hedison.com

 

[maisano]

Linda,
Not sure what is causing the problem. Closing the database with the window 'X' button seems to send our database into fits of corruption. One thing that helped us was to add the option to 'Compact on Close' in the 'Tools' -> 'Options' -> General tab. We can go for weeks now before we run into trouble.

Also have you downloaded Microsofts latest 'JetComp' - it's a very nice utility for fixing corrupt databases - it has always worked for ours - pretty slick.

Good luck,
Paul

 

[raftech]

Ran into a problem with this a while back.

Check the memory in your PC. IT WILL corrupt a database if one of your memory chips are bad.

Rob