S
Sid Singer
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
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