Fix Microsoft Access Errors 3704, 3045, and 3734 in a Split Database
Question details
The user is encountering errors 3704, 3045, and 3734 when multiple users attempt to open or update a shared backend database.
- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Multiple users are accessing a split database simultaneously, and linked-table updates executed during a form's Open event are triggering system conflicts.
- Observed behavior
- The database throws file-use or locking conflicts (errors 3704, 3045, and 3734), preventing the linked tables from updating properly.
Ensure all users have completely closed the database and create a backup of both your front-end and back-end database files before making any VBA or structural changes.
Identify the Failing VBA Statement
Temporarily disable your custom error handlers to allow the Access debugger to pinpoint the exact line of code causing the conflict.
Often, generic error messages hide the specific line of code that is failing. By removing the error handler, Access will pause execution and highlight the exact statement, such as a DoCmd.RunSQL update against a linked table.
Open your front-end database, right-click the form triggering the error, select 'Design View', and click 'View Code' in the ribbon.
Locate the 'On Error GoTo' statement in the form's Open event and comment it out by placing an apostrophe (') at the beginning of the line.
Run the form again to trigger the error. When the system prompts you, click 'Debug' to see the exact line of code causing the 3045, 3704, or 3734 error.
Use a DAO Recordset Instead of DoCmd.RunSQL
Replace bulk SQL update commands with explicit DAO Recordsets to prevent application-level locking conflicts when updating settings records.
Verify Database Open Mode and Access Builds
Ensure the database is configured for multi-user shared access and check your Microsoft Access installation for known version bugs.
Looking for a Reliable and Free Office Alternative?
While Microsoft Access is used for complex relational databases, managing everyday data, reports, and calculations can often be done more efficiently in modern spreadsheets. WPS Office provides a lightweight, highly compatible, and free alternative to the Microsoft Office suite.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the on-screen prompts to set up the software.
- 3. Open and Edit Files: Launch WPS Office to instantly open, edit, and save your existing Office documents and spreadsheets.
Frequently Asked Questions
What causes error 3045 in Microsoft Access?
Error 3045 'Could not use file; file already in use' occurs when the backend database is opened in exclusive mode by another user or process, preventing shared access for other users in the network.
How do I ensure my Access database is set to shared mode?
Go to File > Options > Client Settings. Under the 'Advanced' section, set the 'Default open mode' to 'Shared'. This allows multiple users to access the split database simultaneously without locking the entire file.
Why does DoCmd.RunSQL cause locking issues in a split database?
DoCmd.RunSQL executes queries at the application level, which can sometimes trigger broader table or page locks. Using a DAO Recordset instead allows for more precise row-level locking and faster updates, significantly reducing file-use conflicts in a multi-user environment.
