Apparent Corruption after Machine Rebuild

[JPadley]

I am a self-employed Microsoft Access developer. I have been using Access for over 5 years, but this one has me stumped.
I have an MDB with roughly 50 linked tables, 100 queries, 100 forms, 20 reports and 20 modules. I take regular backups - at least daily. I am used to corruption and usually know how to purge it. However, after a recent machine rebuild, I have found that ALL of my backups appear to be corrupt???
Whatever I attempt to do, I recieve one or more of a range of error messages;

i) The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.
ii) Unexpected error (35012)
iii) GPF

I have tried full and/or partial imports, installing various OCXs, DLLs and service packs, using the /decompile switch, using Access 2000 to do a conversion, DAO Compact, and JetComp. All of these methods meet with partial success at best.

The backups were fine before I rebuilt my machine, and new files work fine, so what the hell is going on???

 

[Rohdem]

Are you familiar with corruption at the record level? This usually occurs in a memo field in one of the records. When you view the record, #ERROR appears in the field. This can cause the first error you listed. I have an Access 97 utility that looks for corrupted records. E-mail me and I'll send it to you.
Mike Rohde
rohdem@marshallengines.com