Access 200 Corruption

[Cleis]

Hi Group:

I've got an Access 2000 application that I'm building and everytime I turn around the db is corrupt. It seems to be happening when I copy and paste onto my thumb drive to bring home. At work, I'm developing on an 2000 version, when I get home I'm on an XP version. I've been carful to use the older versions of the ADO libraries and I'm not using any Active-X controls. I've been very careful to make back-up copies but it's a pain in the ol' keester as I'm tired of re-creating the work that I did at work! I'm pretty sure that the error is coming from mass deletes out of the tables before I bring the db home. My most recent error is AOIndex doesn't exist.

Any ideas on how I can avoid this problem going forward? Is 2000 as stable as XP, 97, or 2.0? Over the years I can count only a handful of times where a db became corrupt? Would it be a correct statement to say that 97 followed by XP was by far the most stable platform . . . my experience would say yes.


Thanks for any insight!

 

[RoyVidar]

I've come to the conclusion that when developing, and not remembering some small precautions, like for instance

* always compile and save before closing
* always compile and save before changing view (VBE/Access)
* always compile and save before running code
* always compile and save before and after importing forms/modules/reports

corruption might sneak up on you, but to me, 2002 (xp) is less stable than I managed to get 2000, which may or may not relate to service packs or other stuff in addition?

I think the AOIndex thingie might be corruption of the system tables (as indicated in this archived post from CDMA

http://www.mailarchive.ca/lists/comp.databases.ms-access/2003-06/1699.html)

JetComp as suggested there, migth do something, else, for code curruption, I'll often paste something like the following, which should contain lot of info on corruption in general, causes, how to prevent - and recover:

This faq Corrupt Microsoft Access MDBs FAQ has a lot of info concerning corruption, symptoms and how to deal with it. MakeItSo's FAQ705-4683 also has some recommandations.

During the last years, I've resolved all my code corruption issues using the /decompile option, in stead of importing objects. It's described here Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times

Here's also an option that might provide some results on exporting/importing database objects Thread705-834817.

Roy-Vidar