Fix Access Query Result Size Errors in Multi-User Databases
Question details
The user needs to resolve an error where a Microsoft Access query result exceeds the maximum database size, typically occurring when multiple users share a single, unsplit database file.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Running complex queries in a multi-user Microsoft Access environment.
- Observed behavior
- Microsoft Access displays an error indicating the query result is larger than the maximum database size, causing the query to fail and disrupting multi-user workflows.
Ensure all users have completely closed and exited the Access database, and verify that you have full read and write network permissions for the shared folder where the back-end file will be stored.
Split the Database Using the Database Splitter Wizard
Splitting the database isolates the data tables from the queries and forms, effectively preventing file size limit errors and file locking issues in multi-user setups.
A multi-user Access database should always be split into a back-end (containing only the tables) and a front-end (containing queries, forms, reports, and macros). This structure drastically reduces network traffic and minimizes the risk of database corruption.
By giving each user a local copy of the front-end, temporary query results are processed on their individual machines rather than bloating the shared database file.
Open your Microsoft Access database file. Navigate to the 'Database Tools' tab on the main ribbon, and click on 'Access Database' in the Move Data group to launch the Database Splitter Wizard.
Follow the wizard's prompts to split the database. When asked where to save the back-end file (which will contain the suffix '_be'), choose a highly reliable shared network drive where all database users have full permissions.
Once the split is complete, Access will automatically convert your current open file into the front-end (containing linked tables). Make copies of this front-end file and install a separate copy locally on each user's computer.
If you ever move the back-end file to a new server or folder, open the front-end database, go to the 'External Data' tab, and click 'Linked Table Manager' to refresh the connections to the new file path.

Simplify Your Document Management with WPS Office
While Microsoft Access is highly specific for database management, handling your daily documents, spreadsheets, and presentations doesn't have to be complicated. WPS Office is a powerful, free alternative that offers a seamless, lightweight experience for all your standard office tasks.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the Software: Run the downloaded installation file and follow the simple on-screen instructions to set up the software.
- 3. Start Creating: Open WPS Office and instantly begin creating or editing your word documents, presentations, and spreadsheets with ease.

Frequently Asked Questions
Why does Microsoft Access say my query result is larger than the maximum database size?
This typically occurs in unsplit, multi-user databases when complex queries generate massive amounts of temporary data. Access has a strict 2GB file size limit, and processing heavy queries directly in the shared file can easily exceed this limit.
Do I have to give every user their own copy of the front-end database?
Yes. Storing the front-end on a shared network drive defeats the purpose of splitting the database. Each user must run a local copy of the front-end on their own computer to ensure stability and avoid network bottleneck issues.
How can I refresh the table links if the back-end database is moved?
In your front-end database, navigate to the 'External Data' tab and select 'Linked Table Manager'. Select all the tables that need updating, click 'OK', and then browse to the new location of your back-end database file.
Can a split Access database be reversed?
Yes. Although there isn't an automated 'un-split' wizard, you can reverse the process manually. Open the front-end database, delete all the linked tables, navigate to the 'External Data' tab, and use the 'Access' import option to import the actual tables back from the back-end file.




