Compacting & Repairing the Database

NOTE: This section does not apply to SQL Server databases.

Compacting & Repairing the database requires Administrative Access to Mouse Tracks.Mouse Tracks stores its data in a Microsoft Access database. The database file it uses is MtrackBE.mdb (as in Mouse Tracks Back End). For performance reasons, when records are deleted from the database, the disk space used by the deleted record is still allocated to the database file. Periodically it is a good idea to compact and repair this file. Compacting the file reduces the amount of disk space the file uses and speeds up queries made to the database. When you compact your database, Mouse Tracks will also check it for errors and try to fix any problems.

Step-by-step Instructions

1. You will need to have exclusive access to the database (mtrackbe.mdb file) for the procedure to start. Make sure all other users have exited Mouse Tracks.
2. From the Tools menu choose Compact & Repair Data Files.
3. A message box will appear showing you the results of the maintenance.

Mouse Tracks creates a backup copy of your database every time you have a successful compact and repair. It names the file mtrackbe.mdb_lgbe (Last Good Back End) and stores it in the same directory as the MtrackBE.mdb file. You should not exclusively rely on this method for a backup copy because a corrupted database may still compact and repair--leaving you with a backup copy that has problems. If you store your data on a server, make sure your network administrator is backing up your Mouse Tracks data directory.

Created using Helpmatic Pro HTML