Others

Set Up a Split Microsoft Access Database for Multiple Users

Khadija KhanKhadija Khan Nov 18, 2026 869 views

Question details

Set up a Microsoft Access database so multiple users can work with the same data through separate local front ends.

Set Up a Split Microsoft Access Database for Multiple Users
Product
Microsoft Access
Device & OS
not provided
Scenario
A team needs to share database tables while each user runs forms, queries, reports, and code from a local copy.
Observed behavior
Each local front end should link to one back end stored in a shared network folder.
Before you start

Make sure all users have closed the database, and identify a shared network folder where they have read, write, create, and delete permissions. Back up the original database before splitting it.

Solution 1Recommended

Split the Access Database and Distribute Local Front Ends

Use the Database Splitter to keep shared tables on a file server and give each user a separate local application file.

The back end contains the tables; the front end contains linked tables, queries, forms, reports, and code. Avoid using an unsplit database or placing the back end in a OneDrive, SharePoint, or other synchronized folder.

1
Run the Database Splitter

Open the database in Microsoft Access and select Database Tools > Access Database. Follow the Database Splitter prompts to create a back-end file in the shared network folder.

2
Check the table links

In the resulting front end, open External Data > Linked Table Manager. Verify that the linked tables point to the shared back end, preferably using a network path such as \\server\share\database_be.accdb.

3
Distribute the front end

Copy the front-end file to a local folder on each user's computer. Have each user open their local copy and confirm that they can view and update the shared data.

4
Maintain the files

Include both the shared back end and the front-end source file in your backup plan. If the back end moves, use Linked Table Manager in each front end to update its links.

Split the Access Database and Distribute Local Front Ends
Consider an ACCDE front end: You can distribute the front end as an ACCDE file to limit design and code changes. Keep the editable ACCDB source for future updates.
Free Microsoft Office alternative

Use WPS Office for Everyday Documents Alongside Access

WPS Office is a free, lightweight alternative for everyday office work, with a familiar interface and support for common Microsoft Office formats to make migration easier. It does not replace or fix a split Microsoft Access database.

Work with Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for documents, spreadsheets, and presentationsKeep reports and spreadsheets in common formats alongside your Access workflowInstall a free, lightweight office suite for everyday tasks
microsoft office alternative - wps office

Frequently Asked Questions

Why should each user have a local Access front end?

A local front end lets each user run forms, queries, reports, and code from their own copy while the tables remain shared in the back end. Sharing one unsplit file increases the risk of corruption.

Can I put the Access back end in OneDrive or SharePoint?

Do not place the back-end file in OneDrive, SharePoint, or another synchronized folder for this setup. Store it in a shared network folder on a file server instead.

How do I relink tables after moving the back end?

Open each local front end in Access, select External Data > Linked Table Manager, and update the linked tables to point to the back end's new shared network path.

What permissions do users need on the shared folder?

Users need read, write, create, and delete permissions in the shared network folder so Access can use the database and its locking file.

Should I distribute an ACCDE or ACCDB front end?

An ACCDE can limit changes to the front-end design and code. Keep an editable ACCDB source so you can make changes and create updated ACCDE copies.