How to Split a Microsoft Access Database (Step‑by‑Step Guide)

Splitting a Microsoft Access database into a front‑end and back‑end is the single most important step for improving performance, reducing corruption, and supporting multiple users. This guide walks you through the process safely and correctly.

A split database is the foundation of every stable, multi‑user Access application. If your database is slow, corrupting, or difficult to update, splitting it is almost always the first fix. This guide explains what splitting means, why it matters, and how to do it properly.

What Does “Splitting” a Database Mean?

When you split an Access database, you separate it into two files — one for data and one for the user interface. This dramatically improves performance and stability.

• Back‑End (BE): Contains tables and data
• Front‑End (FE): Contains forms, queries, reports, macros, and VBA

Each user gets their own FE copy. The BE stays on the shared network. This prevents file collisions and reduces corruption.

Why Splitting Is Essential

Running a single, unsplit Access file from a shared drive is the #1 cause of corruption and slow performance. Splitting solves most multi‑user issues immediately.

• Reduces corruption dramatically
• Improves multi‑user performance
• Allows independent updates to the front‑end
• Prevents file collisions
• Enables SQL Server migration later

We can split your database for you →

If your database is also slow, review How to Fix Slow Access Databases for additional optimization steps.

How to Split a Microsoft Access Database

Follow these steps carefully to split your database using the built‑in wizard:

1. Open your Access database (ACCDB or MDB)
2. Go to Database Tools → Access Database (Split Database Wizard)
3. Choose a location for the back‑end file (usually a network share)
4. Access creates a new BE file containing all tables
5. The original file becomes the FE
6. Distribute the FE to each user’s workstation

After splitting, the FE links to the BE tables automatically. You can verify links using the Linked Table Manager.

Deploying the Front‑End to Users

Each user must have their own local copy of the FE. Sharing a single FE from the network will cause corruption and slow performance.

• Place the FE on each user’s PC (Desktop or Program Files)
• Use a simple batch script or updater to push new versions
• Never share the FE from a network drive

For automated deployment, see Access Deployment Automation (Auto‑Updater).

Best Practices After Splitting

Once your database is split, follow these best practices to maintain performance and stability.

• Compact & Repair the BE regularly
• Use record‑level locking
• Avoid Wi‑Fi for multi‑user Access
• Keep the BE under 1GB when possible
• Move large tables to SQL Server

For indexing guidance, see Access Table Indexing Best Practices.

When to Upgrade to SQL Server

If you have more than 5 users or large datasets, SQL Server is the natural upgrade path. Access remains the front‑end, but SQL Server handles the data.

• Better concurrency
• Reduced corruption risk
• Improved performance
• Cloud or on‑prem hosting

Learn about Access → SQL Server migration →