Data Corruption

[Guest]

I have converted a multi-user app from Access 97 to Access 2003. This app
consists of two mdb's. A front-end for the user interface and a back-end
containing the data - on a network drive. They are linked using Link Table
Manager.

After a front-end user makes changes to existing data, or enters new data in
the database, and the app is run again, the following situation occurs. A
message pops up stating 'Unrecognized file format. Unable to open database.
Compact and repair database.'

This is despite there being no errors generated in the original transaction.
If we do a compact and repair on the back-end database and then run the
system, it works fine. That is until the process is repeated in a subsequent
data entry situation.

There doesn't appear to be any reason for the back-end data corruption. How
do I deal with this.

Sid Singer

 

[Allen Browne]

See:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

There are several issues listed there that apply in JET 4 that did not apply
in Access 97.

 

[Guest]

Allen,

Thanks for your prompt response. You have an impressive list of tips!
I will implement some of your tips and see if that makes a difference. Since
there's no way to get an accurate determination if a particular tip does the
trick, other than to try it and see if it makes a difference over time, I'm
not able to rate your response at this time. I will get back to you if I
determine that any one particular tip does the job.

 

[Walt Hall]

It seems you hava a corrupted record

I have run into this many times

You will have to physically place your mouse cursor on first record in the
database, and then press down arrow until you get to the end

If there is a data corruption - you will notice the cursor stop in its track
- and will not continue - You should delete that record - try to save or
copy what you from it

If you get to the end of the database without any problems - then try again
- but this time - more slowly - and look out for corrupted characters like
boxes, and swingly signs and what have you - that record is usually
corrupted - you will have to delete it

Sorry - but that is the nature with MS and their bug ridden systems.

Good luck