Splitting a single Back End file into multiple Back End files
Sometimes a MAD has a large number of static reference tables (those whose values are not changed as part of the day to day system use) that are stored in the Back End file. The system can often be made more efficient if these tables are stored in their own Back End file. The Front End will then link to two Back End files. Option 1) could be performed at the same time.
Why would you split the back end database into multiple files?
There are many reasons why you might do this:
- Performance - you can place data that is not used very often into another file. This will improve the performance of the main file.
- Secuirty - sensitive data can be placed into in own database. Access to this database file could then be kept in a secure server. The application can still access it.
- Reduction of redundancy - if your database contains data that is shared by multiple applications you move that into a separate database and each applications can link to it..
- Microsoft Access Limitations - an Access database can be up to 2GB. If your application is reaching that limit you will need to split your data file.