File server databases like Access/JET MDB and ACCDB files need to be periodically compacted and repaired for optimal performance and to minimize database corruption. This also eliminates database bloat that can occur as data is added and deleted in the database.

Microsoft Access databases can be manually compacted from the Access menu. Unfortunately, over the last few versions of Access, the location of this command has moved around driving Access many users and developers crazy. Read our paper on Microsoft Access Database Compact and Repair to Minimize Corruption and Avoid Bloat (by Access Version).

If you create or take over a Microsoft Access application from someone else, you become responsible for the data in addition to the application and its queries, forms, reports, macros, and module code. Unanticipated disasters can occur, so it’s important to prepare before they happen. The amount of effort and investment to spend for disaster recovery varies with the value of the application, but some basics apply to all applications.

A Disaster Recovery Plan is much more than making backups of your database. And if your backups are on the same machine and/or hard disk as your production database, that doesn’t qualify.

Read our paper on Creating a Backup and Disaster Recovery Plan for Microsoft Access Database Applications for ways to limit your risk and headaches, while providing a professional solution for your end-users, boss, and clients.