Office Apps Crashing

Fix Microsoft Access Crashes When the Front End Is on a Network

Nimra MalikNimra Malik Nov 13, 2026 868 views

Question details

The user needs to troubleshoot intermittent Access crashes when a database front end is stored on a network.

Fix Microsoft Access Crashes When the Front End Is Stored on a Network
Product
Microsoft Access
Device & OS
not provided
Scenario
A draft front end containing new VBA code is opened from a network location, while the production front end is stored locally.
Observed behavior
The draft front end intermittently crashes and restarts, sometimes prompting repeatedly for the database password. The local production front end does not show the same behavior.
Before you start

Identify the front-end file, the shared back-end file, and the network path to the back-end tables. In Access, open File > Account > About Access to record each user's version and build.

Solution 1Recommended

Give each user a local Access front-end copy

Use local front ends with a shared network back end to avoid having users run the same front-end file from the network.

1
Check the database split

Open the front end and confirm that its shared tables are linked to the back-end database. In the Navigation Pane, linked tables typically have an arrow beside their icons.

2
Copy the front end locally

Close Access and use File Explorer to copy the front-end file to a folder on each user's computer. Leave the shared back-end file on the network.

3
Check linked tables

Open each local front end and use External Data > Linked Table Manager to verify or update links to the shared back-end file.

4
Test the draft

Run the same forms and actions that previously caused a crash. Distribute a separate updated local front-end copy to each user when the draft is ready.

Give each user a local Access front-end copy
Check network access: Users need appropriate permissions to the back-end file and its folder, including the ability to create and modify the Access lock file. A local front end alone does not resolve VBA errors.
Free Microsoft Office alternative

Use WPS Office for Compatible Documents and Spreadsheets

WPS Office is a free, lightweight alternative for everyday documents, spreadsheets, and presentations, with a familiar interface that helps users move their files between office suites. It does not repair Access crashes or replace an Access database and its VBA application.

Open and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXWork with exported spreadsheet data when an Access database is not neededUse a familiar interface for common office tasksMove compatible files between WPS Office and Microsoft Office
microsoft office alternative - wps office

Frequently Asked Questions

Why should each user have a local Access front end?

A separate local copy avoids having multiple users run the same front-end file over the network. Keep the shared data in the network back end and verify the links through External Data > Linked Table Manager.

Where can I find VBA compile errors in Access?

Press Alt+F11 to open the VBA editor, then choose Debug > Compile. Fix the highlighted error and repeat until the project compiles.

Does moving the front end locally fix repeated password prompts?

It may prevent prompts associated with a crash and restart, but it does not guarantee a fix. Test the local front end and investigate the password and network access separately if prompts continue.

How do I check which Access build each user has?

In Access, open File > Account > About Access and record the version and build. Compare the results across affected and unaffected users.

Can WPS Office open and run my Access front end?

WPS Office is not a replacement for an Access database application or its VBA code. It can work with compatible exported files, such as XLSX spreadsheets, but it does not fix the Access front-end crash.