Microsoft Access Audit Checklist
The favored Microsoft Access has spawned many administrative systems. Nowadays Disk drives and networks are inherently stable - leading to a feeling of misplaced comfort. Few monetary officers are aware that just a flicker of the power can cause a complete loss of knowledge - and may threaten the viability of the company.
The Microsoft access database design "Compact and Repair Database" facility could overcome the problems caused by a crash. Relinking the Back-End Database can also help. But typically, relying upon the extent of the interior corruption, recovery may be impossible.
A serious cause of knowledge corruption
After person activity, the Front-End and Back-End Databases swell up in size. When many months have passed, these databases could develop to more than double the unique size - if compaction will not be recurrently carried out.
And if a Microsoft Access Database has not been compacted for a while, the chance of an irrecoverable crash is highly likely, if not inevitable.
Here is a list of essential things to do to minimise the chance of knowledge corruption and the next impact, after a crash:
Set all the Entrance-End Databases to automatically compact on exit
Make a Backup of the Back-Finish Database on a regular basis
Compact the Back-Finish Database after the Backup
The Backup must be stored off-site
Frequently test that the Access Database can be recovered from the Backup
Without these steps, a company will be at financial risk.
Note that the Back-Finish database should not be set to automatically compact on exit. Nonetheless it is attainable to create routine to automate the compaction of the Back-Finish database.
How much Downtime can you afford?
The frequency of the Backup relies on the fee and inconvenience of re-entering data because the last Backup. If a Backup is completed day by day, then on a crash, the maximum of a whole day's work will need to be redone.
Finagle's corollary to Murphy's Regulation: Anything that can go wrong, will - and at the worst doable time
This worst case situation (i.e. having to re-enter a whole day's work) is most certainly to happen on heavy month-finish processing.
If re-entry of data shouldn't be practicable, then a conversion of the Back-End Database to SQL Server will grow to be necessary. SQL Server will assure that no data will be lost. There may be no such assure with a Microsoft Access database where transactions should not logged.
Most corporations would not have the need to log every change made to an Access database. Nevertheless it's essential to log some primary data on the final change made to a record. At a minimum this ought to be User ID, Date and Time of the change.
After all, with SQL Server, all modifications could possibly be automatically logged using a Trigger.