VB6/Access97 application. For the most part my multi-user application works fine, but occasionally the database gets corrupted, or dubious data is generated.
I'm creating a Database Maintenance form whereby Users can monitor the back end database and check all is well. I'm putting in routines to tidy up tables if known errors have occurred. There is also a standard DAO Compact and Repair facility ( much better I've found than using ADO/JRO ).
Now, is there a way of telling whether a database is so corrupted/damaged that C & R won't work? I looked at one the other day that I couldn't repair and the only way to restore it was to create a new database and import the tables in. The application was still working, so although Access recognised it had a problem it wasn't preventing normal reading and writing of data.
Can VB look at an Access database and tell whether it's OK, slightly corrupted and in need of C & R, or so corrupted that needs a blank database transfer?