MS Access™ MVP Awardee: 2007--2019
Visit My Blog: GPG on Access
My Published Books:
Professional Access 2013 Programming with co-authors Teresa Hennig, Ben Clothier and Doug Yudovich. Grover Park George On Access MS Access™ in a SharePoint World with co-authors Tim Runcie and Ben Clothier.
Most Access developers split their databases into two parts before putting them into production. This is important because it's the only safe way that more than one person can use it. One part, usually called the "Front End", is an an accdb file containing the forms, reports, queries, macros and code modules. The other part, usually called the "Back End", is an accdb file containing only the tables. Users open only the front end. The tables in the back end are linked to the front end. There are a few advantages to split databases. Controlling Access to Shared Data. The back end data files can be placed in a shared folder to which only authorized users have access. Each user or user group can then be given copies of the front end with different features. For example, data entry users can have a front end with forms designed to add, modify or delete data, while managers can be given a front end whch includes only reporting functions. Improving Performance. Having the front end on a local PC, with the back end in a shared folder, can improve performance. Updating the Database. Because the data tables are separated from the interface objects, it is easy to create and distribute an updated user interface without having to worry about losing existing records in the back end. Access has a Database Splitter Wizard in the Ribbon, available from "DATABASE TOOLS --> Move Data --> Access Database" which will walk you through the process of splitting your database. You should do this after the database is created and before it is distributed for production.