Repairing data corruption using external Jetcomp4.exe

Sometimes a data verification will produce a message indicating that an error has occurred in a data file and the standard repair will not work. Note the name of the data file (something.mdb) and proceed as follows.

Note: the following repair process can cause loss of data. To determine if records have been lost you could note down the number of inventory and contact records that are in your tables before carrying out a repair and checking them again after it finishes. This is particularly important for invoices/credits, stock and Contacts (all in stocktbl.mdb) but can be carried out for any tables. Use the view/find command with no criteria to see a view of all records. Note the number of records returned.

Steps to repair a corrupted mdb file

• Make sure nobody is using the database (check client machines if in multiuser mode).

• Make a copy of the original file that is corrupted. Save it to another folder, just in case!

• Rename the original corrupted file to something like fnameCorrupted.mdb (where fname.mdb is the file noted above. For example you would rename mydata.mdb to mydataCorrupted.mdb).

• Start Jetcomp4.exe (this should be on the distribution CD. If it is not it is possible that it has not been installed on your system. To install see below) in Explorer by double clicking on it.

• A UI is displayed. Select the SOURCE file to verify and repair. This is the file you renamed above (in our example mydataCorrupted.mdb). Use the browse button to navigate to the file and select it.

• In the DESTINATION field select the SAME file and remove the Corrupted extension (i.e. rename mydataCorrupted.mdb back to mydata.mdb in the destination field)

• Under the tools menu select the System Database Location – Navigate to the dbfs folder under BookMine and select BookMine.mdw.

• Under the tools menu select Specify User and Password – enter the username and password you normally enter when starting BookMine.

• Click the Compact button.

• A message similar to the one received when you did the standard verify in Bookmine will be displayed referring to the fnameCorrupted.mdb file. This is ok. The destination file should now be free of errors and it should have the same name as the original file that was corrupted. This is essential.
• Start Bookmine and verify your data again. If there are no errors then the corruption has been fixed.
• If all is ok delete the file that was renamed to corrupted from the disk.
• Some errors cannot be fixed in this way. It is possible that you will have to have the file fixed by InfoMining. The standard hourly rates apply to any such work.

• Infomining cannot do anything to ensure that your data is free of errors. This is your task. Regular verification and backups are essential. Treat it as being as important as locking your premises every night. Only you can ensure it is done!

Installing Jetcomp.exe

To install you will need a file called JetComp.exe (look on distribution CD or get from InfoMining). Shut down all other applications. You must have Office 97 Sp1 and Sp2 or later installed before installing JetComp.exe.

To install Double click on JetComp.exe. This will install a file called Jetcomp.exe in your Windows\System or WinNT\System folder which you use to reapir corrupt data files.