Microsoft Access Audit Checklist
The popular Microsoft Access has spawned many administrative systems. Nowadays Disk drives and networks are inherently stable - leading to a sense of misplaced comfort. Few financial officers are aware that just a flicker of the ability can cause a whole lack of knowledge - and may threaten the viability of the company.
The Microsoft Access "Compact and Repair Database" facility might overcome the issues caused by a crash. Relinking the Back-Finish Database may additionally help. However usually, depending upon the extent of the inner corruption, recovery could also be impossible.
A major cause of information corruption
After consumer exercise, the Entrance-End and Back-Finish Databases swell up in size. When many months have passed, these databases could develop to more than double the original dimension - if compaction is not recurrently carried out.
And if a Microsoft Access Database has not been compacted for some time, the chance of an irrecoverable crash is highly seemingly, if not inevitable.
Here is a list of important things to do to minimise the prospect of data corruption and the next impact, after a crash:
Set all of the Entrance-Finish Databases to automatically compact on exit
Make a Backup of the Back-End Database frequently
Compact the Back-Finish Database after the Backup
The Backup must be stored off-site
Repeatedly test that the Access Database could be recovered from the Backup
Without these steps, an organization might be at monetary risk.
Note that the Back-End database should not be set to automatically compact on exit. Nevertheless it is possible to create routine to automate the compaction of the Back-End database.
How a lot Downtime can you afford?
The frequency of the Backup is dependent on the associated fee and inconvenience of re-coming into knowledge since the final Backup. If a Backup is completed each day, then on a crash, the maximum of an entire day's work will should be redone.
Finagle's corollary to Murphy's Legislation: Anything that may go mistaken, will - and on the worst potential time
This worst case state of affairs (i.e. having to re-enter a whole day's work) is most certainly to happen on heavy month-end processing.
If re-entry of data shouldn't be practicable, then a conversion of the Back-Finish Database to SQL Server will grow to be necessary. SQL Server will guarantee that no information might be lost. There might be no such guarantee with a Microsoft ms access database database where transactions will not be logged.
Most companies do not have the necessity to log each change made to an Access database. Nevertheless it's important to log some primary information on the final change made to a record. At a minimal this must be Person ID, Date and Time of the change.
In fact, with SQL Server, all changes could be automatically logged using a Trigger.