The Database Maintenance form requires Administrative privileges to access.

This form is provided to maintain a manageable database. After using Mouse Tracks for some time, you may notice that some of the forms take longer to load. This is most likely caused by an increased size in your database. When Microsoft Access queries a table, it must load the entire table to memory before it can process the records.  SQL Server handles this more efficiently with larger databases by only returning a subset of the rows (assuming the recordset is filtered). If you're using an Access database, try Compacting & Repairing the database to improve performance. You can also reduce the size of your database by pruning old records. To prune records from the database, select Prune Tables from the Tools menu.

Pruning Tables

Delete Disposed Equipment Records older than - When you dispose of computer or peripherals, the entire record is not actually deleted from the database. For tracking purposes, the records are moved to the Disposed table. This table is rarely accessed from Mouse Tracks.  If you wish to delete records from this table, you must do so from this form.

Delete Closed Help Desk Tickets older than - If your help desk is highly used, over time this table will grow very large. After several years, the information in your old help desk tickets becomes less valuable and you may want to prune some records from this table.

Delete Closed Purchase Orders older than - If your purchase order system is highly used, over time this table can also become very large. You most likely would only need to track these purchases for three to five years. After which, you may want to prune some of these records.

Reset List Columns for user - You may never need to use this option. The list column settings for Mouse Tracks Users are stored in your database. If for some reason they were to get deleted or corrupted, select their User ID from the drop down list and then click the Execute command. The next time the user logs in, his list column settings would be rebuilt.

Fix Database Referential Integrity Discrepancies

Mouse Tracks enforces referential integrity between your tables. For example, if a user ID was deleted from the database, the computer allocated to the user ID would become Un-allocated because Mouse Tracks would set the allocation field (compUserID) to a Null value. However, if for some reason, another Mouse Tracks user was editing this computer record at the same time the user ID was deleted, the form would still show that the computer is allocated to this user. If the user who opened the computer record canceled his own update, there wouldn't be any discrepancies. However, if he saves the record, the computer would still be allocated to the deleted user (assuming he didn't change this part of the record). As you can probably tell, the odds of this happening are fairly minimal. However, just to be safe, Mouse Tracks includes this feature as a way to detect and fix these discrepancies.

Mouse Tracks will warn you about the number of records the query would delete. You will have the option of canceling the update query if you change your mind. Mouse Tracks fixes the discrepancies by setting the mis-matched values to null. If desired, you may choose to cancel the automated fix to investigate and/or manually fix the records in question.