Dealing with corruption errors

[olly]

I would appreciate anybody's thoughts on the following problem.

I have recently developed an Access application using Access 97 which
I have to provide to Access 2000 users as well. To give you an idea of
the size of the application, there are about 120
forms/queries/tables/reports and some, but not a lot of, VBA.

I am encountering problems when converting the application from 97 to
2000, in that individual objects are becoming corrupted. It has
happened to about 4 objects, and each time I've had to revert to an
earlier, backed up version of the object and then recreate the
developments on that object.

It does not appear to be related to a particular installation of
Access, since I've tried the conversions on various machines with the
same result.

My guess is that early on in the development process, the application
became corrupted, and now it manivests itself periodically in
different objects. I have tried decompiling but this does not help.

My question is, should I try to rebuild the application from scratch?
If so, how is this most efficiently achieved? Or is there another
option?

I appreciate this is quite an open ended question, any thoughts would
be appreciated.

Thank you.

[Lyle Fairfield]

oj*@mailinator.com (olly) wrote in
news:d7**************************@posting.google.c om:

My guess is that early on in the development process, the application
became corrupted, and now it manifests itself periodically in
different objects. I have tried decompiling but this does not help.

I would try saving as text each object which corrupts, and loading it back
in as text (from within AC2K). If it loads and compiles then you can,
probably, exclude code error from your investigations. It's likely you
know how to do this; code is available to save the whole db and load it
back into a new db at http://ffdba.com/downloads.htm if you don't; it's
also available there if you do.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)