5.10.1 Overview
Over time, Microsoft Access databases grow in size. The database not only contains records but also "wasted" space from frequent data changes. To avoid generating excess amounts of wasted space and corrupting your database, you must compact your database periodically. A more detailed explanation of why doing a repair and compact of a database is necessary are found in these links:
http://office.microsoft.com/en-us/access-help/help-prevent-and-correct-database-file-problems-by-using-compact-and-repair-HA010235583.aspx
http://office.microsoft.com/en-us/access-help/compact-and-repair-an-access-file-HP005187449.aspx
5.10.2 Log users out of Latitude
Make sure everyone is logged out of Latitude before proceeding to the next step to avoid errors.
5.10.3 Backup your database
Before doing the Repair & Compact, back up your database first.
For more information on how to Backup your database, refer to the 'Protect your data from loss' Category Topic.
5.10.4 Repair & Compact
You must be logged in as an Admin user
From the Home screen, click Administration and then select Attach
Click Repair & Compact button and wait until you get the message 'Repair & Compact of Data file is complete'
Click ok and the click Close button
5.10.5 Error: Database already exist
While doing the Repair and Compact, if the error message 'Database already exist' appears and clicking "OK" just shows 'Compacting Database' but it does not do anything.
FIX:
Using 'My Computer' or Windows Explorer, go to your Map drive where the Latitude database is located
Check if there is a Latidata.BAK or Latidata.TMP file in the directory
If there is one, rename it as zzLatidata.BAK or zzLatidata.TMP
Attempt to do the Repair & Compact again
If the process is successful, you can delete the zzLatidata.BAK or zzLatidata.TMP
If the process still fails contact technical support
5.10.6 Error: File already in use
While doing the Repair and Compact, the error message 'Could not use 'path\Latidata.mdb'; file already in use' appears and clicking OK will just show 'Compacting Database' but it does not do anything. This means that someone is still on Latitude, not logged out properly or the workstation/server was not able to update the status.
Using 'My Computer' or Windows Explorer, go to your Map drive where the Latitude database is located and check if there is a Latitude.laccdb or Latidata.ldb file.
FIX: 1
Right click on the LDB file and delete the file
If you cannot delete it because it says file is in use, then copy it into your My documents folder
Open the file using Microsoft Word
It will tell you the computer name/user
Get the user/workstation to check if Latitude is still on. If not then restart their workstation
Check again and attempt to delete the ldb file
If you cannot, then a server restart maybe required.
FIX 2:
Click Administration –> Setup –> Other tab –> User currently logged in –> dropdown list to see who is still on Latitude.
Ask these users to log out & close Latitude
Once users are confirmed logged off, also close your copy of Latitude if you still have it running
Delete the Latidata.ldb file
If you cannot delete the file then check setup again and see who else is still on the list
Sometimes users log out of Latitude but Microsoft Access is still running in the background. This happens when the workstation cannot resolve/update its system processes.
Once the LDB file is deleted, attempt the Repair & Compact again.
5.10.7 Error: #Deleted# or ######### on all fields
After performing a Repair & Compact, opening the Client or Job screen shows the first record with all fields containing hashes or pound symbols. This is a corruption caused by not closing Latitude properly, power interruption or intermittent connection issues.
FIX:
check all the tabs and register and if no data appears delete the record.