Mysterious Corruptions and Why....

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

I've got a theory on this....

8 months ago I almost lost my database(s) due to frequent and unexplained
corruptions. I discovered I could recover those databases 100% of the time,
but also discovered that on occassion the corruption would mysteriously crop
back up (sometimes more than once in a single day).

Fortunately I think I've solved MY particular mystery. I can't say for sure
that'll it's true for everyone, but it revolves around the use of DAO 3.6.
I realize that most are using ADO by now, but I'm not. I had used DAO 3.52
for a long time and did most of my coding there.

Ultimately I changed the reference to DAO 3.6 in order to use the most
current stuff (no other real reason). I probably changed it before a
weekend or something because I only recently figured it out....

Compacting (and probably compiling) while DAO 3.6 is the reference regularly
caused corruption. Of course other things did too but the act of compacting
did it regularly.

However, once the db is salvaged, and the DAO 3.52 reference restored....
it doesn't corrupt!

Can anyone else confirm my suspicion??

Best Regards to all,
Eric
 
If you are using Access 97, then yes, referencing DAO 3.6 will cause
problems.

Access 97 uses Jet 3.5, and DAO 3.5x is designed to match.
Access 2000 and later use Jet 4, and DAO 3.6 is designed to match.
Using the wrong library for your version of JET is inviting trouble.

Thanks for posting your resolution.
 
Back
Top