Repairing an Access (Jet) Database

TSB1023 | Tuesday, 10 September 2002

finPOWER, emPOWER and fdPOWER can use either a Microsoft Access or Microsoft SQL Server database. Access databases may become corrupt due to a number of different factors. The symptoms of a corrupt database can range from run-time errors whilst processing data to the complete inability to open the file in the finPOWER, emPOWER, fdPOWER or even in Access.

Please note that backups form the most important defense against database corruption. If your database is corrupt and cannot be repaired the only option is to restore to a backup.

WARNING: The only 100% safe thing to do after an Access database corruption occurs is go back to a good backup.

WARNING: Do not forget to question why the corruption occurred. Was it a power failure, bad/ suspect hardware, Opslock? If you do not isolate a problem database corruptions may occur over and over again. See TSB1019 for more information on possible causes of database corruption.

Restoring from a Backup

A very important point to consider when restoring from a backup is that if that restore fails and overwrites the "corrupt" database you could be left with nothing. Always rename the existing corrupt database before restoring, rather than restoring over the top of it.

Even after a restore, the corruption may still be present. It may be that the "corruption" event occurred some time ago, and will only show its head when running a particular process. So, you must check the database is ok after restoring. For example in finPOWER run the Loan and/or Deposit Exception Reports, Loan Detail Report, Loan Control Report etc. The Loan Detail Report, for example with all options checked, retrieves a lot of information and if the database is still corrupt may crash.

Repairing a Database

If you cannot or will not go back to a backup then the alternative is "repairing" the database. Remember the only 100% safe option is to restore to a good backup.

Note: Intersoft charges time and costs for checking and/ or fixing databases. There is also no guarantee that a database can be successfully repaired, or that all existing information can be saved intact.

Send the database to Intersoft for Repairing and Testing

You should contact your local Intersoft Dealer or Intersoft directly to establish the best way to repair your database, including how to physically get the database to Intersoft, eg ftp internet access, email or courier and acceptable media format. Depending on available resources at Intersoft a database can normally be repaired and tested within a few hours.

Notes.

  • You will be out of action until we can return the repaired database.
  • If you do decide to continue processing (if you can) then:
    • Limit the amount of work done until we have tested the database.
    • Note everything that is entered, in case the database is still corrupt and needs to be rekeyed.
  • There is no guarantee we can successfully repair the database.

DO NOT ATTEMPT TO REPAIR THE DATABASE YOURSELF

If you attempt to Repair the database yourself you may only make things worse.

Remember an Access "Compact and Repair" will only fix the database structure and records; it cannot take into account the meaning of data.

For example:

  • In finPOWER if a Payment Schedule record is corrupt the repair may delete the record - but this may now mean the Loan's Balance does not equal the remaining payments on the Payment Schedule.
  • A Repair may drop indexes and relationships if they can't be rebuilt. This can mean continuing to use the database will "corrupt" the data over time. Eg, if the relationship between a Loan and Transaction is broken and the Loan code is changed then the Loan loses all its Transactions as the Transactions aren't moved with the Loan.

Both of these situations have occurred in the past.