Resolving database problems |
  
|
Resolving database problems |
|
Occasionally an Access database may exhibit unexpected bahaviour (usually due to some network issue while saving data), or the user may have customised it in ways that are later found to be undesirable.
In the case of an issue with an Access database the following proceedures should be followed:
Firstly:
•attempt a Compact and Repair in ESdat (File - Compact and Repair), or in Access (Tools - Utilities, or Office Button - Manage)
or
•for more serious issues use the JETCOMP.exe utility available from Microsoft (at http://support.microsoft.com/kb/295334/en-us at time of publishing)
If you need to move the data to a new database, this can be done by either:
•the ESdat Data Interchange File (EDIF) export. Generate the file and import it into a new database, or
•export to Excel, then import to a new database, or
•use Access based or other utilities to migrate the data
These issues don't apply to SQL Server databases, which aren't exposed to network issues (as far as database integrity is concerned), and don't provide for general users to make customisations.
In the case of an issue with a SQL Server database a backup should be made and support@esdat.com.au contacted for guidance.