Compact Microsoft Accessâ databases on a scheduled basis. For Windows 95 / 98 / NTâ.

Microsoft Access databases can become corrupt when the database engine begins writing data to the database but is abnormally terminated before completing the write operation. This may happen when there is a power failure or hardware failure. The database engine sets a flag before starting a write operation and then resets it on successful completion of that write process. 

• In Microsoft Jet 2.x databases it was recommended that a repair be used before compactions to ensure that the database was not corrupt.

 
• Do not use the repair option on replicated databases as this will stop the database from being replicable The following reference is from Microsoft press.

"Do not use the RepairDatabase method on a replicated database. If you do, the database is no longer replicable and you will not be able to syncronize it with other replicas in the replica set.  If you suspect that a replica is corrupted, delete the replica and recreate it from another in the set."
"Microsoft Jet Database Engine Programmer's Guide 2nd Ed." Microsoft Press 1997.
A more detailed description can be found at: http://premium.microsoft.com/msdn/library/books/techlang /dnjet/c13_body_2.htm
 
• This operation is not necessary for Microsoft Jet 3.0 or 3.5 databases. Except where an error message indicated that a repair is required. 

A more detailed description can be found at:  http://premium.microsoft.com/msdn/library/officedev /office/html/databasemaintenance.htm