Dealing with Access object corruption...

K

Kenny-Z

Hi group,

at least on my setup (Access2K/Win98SE), I've noticed a tendency for
Access objects to become corrupt, mainly forms and/or their associated
VB modules... Typical error messages that occur when trying to run a
form or view its code are along the lines of "You canceled the
previous operation... (no I didn't), or "Error accessing file. Network
connection lost..." (what network?). Obviously these useless error
messages are resulting from some unexpected situation (file
corruption?). Also, errors may fly referring to a form that has been
deleted from the Database window. Decompiling and repairing the file
never seems to help; only frequent backups can save the day-or at
least part of it. But then you need to identify all of the corrupted
objects and transfer only the good objects to a new container (mdb).
Good times.

But that's the problem-it seems I've had to get into the habit of
saving a backup of the original file before nearly every change made
to a form. You may later discover your backup has ended up with
corrupted objects! Multiple, frequent backups it is.


I'm wondering if other developers have had the same problems and if
there are any general recommendations on how to minimize corrupting
mdb files.

thanks for reading,

kz
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top