1. Splitting a Database: How and Why
Roger Smeaton

2. CONTENTS
Two database architectures
Why split?
How is it done?

3. One-file architecture
Access database
Tables
Relationships
Forms
Queries
Reports
Macros
Modules (VBA code)
Only one database file, has it all!

4. Two-file architecture
Front-end – the user interface
one copy for each user
Back-end – the data
one shared copy

5. Forms Queries Reports Macros Modules (VBA code)
Tables
Relationships
Front-end
Back-end

6. Why split a database ?
Separates data (back-end) from application (front-end).
Developer can make changes to the application without disturbing the data or the users.

7. Why split a database ?
2. Ability to create temporary tables in the front-end. Temporary tables store intermediate results, run-time parameters, etc.

8. Why split a database ?
3. Performance. Each user has a copy of the user interface (in the front-end), so network traffic is reduced.

9. Do I have to split? Not necessary to split if
Front-end is stable (no changes) and
Single-user database

10. When to split
After you have designed your tables & relationships, forms, reports, etc. but before you release the software to the users.

11. How to split a database
OPTION 1 – use the Database Splitter wizard on the Tools menu
OPTION 2 – do it manually [details omitted]

12. Split the demo database Northwind.mdb

17. After you split … Compact the front-end file
How? From the Tools menu, select Database Utilities  Compact and Repair Database

18. Ready to deploy the database?
Copy the back-end to a shared network device.
Re-link the tables in the front-end. Then they will point to the actual data tables in their new location. Tools menu, select Database Utilities  Linked Table Manager
Copy the front-end to each user’s PC.