Use a Split Access Database Without Mapping a OneDrive Drive
Question details
Use a split Microsoft Access database remotely without relying on a mapped OneDrive drive.

- Product
- Microsoft Access and OneDrive
- Device & OS
- not provided
- Scenario
- Multiple users need remote access to a split database with an Access frontend and a shared backend.
- Observed behavior
- OneDrive synchronization is not a reliable way to share an Access backend among concurrent users and can lead to slow performance, unsaved changes, or corruption.
Identify where the Access backend is stored, how many people need concurrent access, and whether a server is available on the backend's local network. Check that users can access a network share or an appropriately secured SQL Server before choosing a solution.
Run Access remotely on a server connected to the backend
Use Remote Desktop or RemoteApp when the Access backend can remain on a shared network location near the server.
Access opens a shared file backend over a network file share, not through OneDrive synchronization. Running the frontend on a server connected to the backend's LAN avoids sending database file traffic over a remote user's internet connection.
Move the backend database to an SMB file share on the server's local network rather than a OneDrive-synced folder. Give users the folder permissions needed to open the database and create and remove its locking file.
Open the frontend in Access and use Database Tools > Linked Table Manager to relink the tables to the backend through a UNC path such as \\server\share\backend.accdb. A mapped drive letter is not required.
Place a separate copy of the frontend in each user's profile on the Remote Desktop server, outside any OneDrive-synced folder.
Have users connect to the server with Remote Desktop or launch the published Access application through RemoteApp, then open their own frontend copy. Test concurrent edits before deployment.

Migrate the Access backend to SQL Server
Use a client/server backend for larger or distributed deployments while keeping Access as the frontend.
Use WPS Office for everyday documents and spreadsheets
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 Microsoft Access or fix Access backend connectivity.

Frequently Asked Questions
Can multiple users open an Access backend from a OneDrive-synced folder?
It is not a reliable multiuser setup. OneDrive synchronizes file copies rather than providing the shared file locking Access needs, which can cause conflicting changes or corruption. Use an SMB share on a LAN or migrate the backend to a client/server database.
Do I need a mapped drive for a split Access database?
No. In Access, use Database Tools > Linked Table Manager to link tables through a UNC path such as \\server\share\backend.accdb, provided the frontend can reach the SMB share and has the necessary permissions.
How can remote users access the database without opening the file share over the internet?
Run the Access frontend on a Remote Desktop server connected to the backend's LAN. Users can connect through Remote Desktop or a published RemoteApp instead of opening the backend file directly from their remote devices.
Can I keep my Access forms after moving the backend to SQL Server?
Yes. Access can remain the frontend with its forms linked to SQL Server tables through ODBC. Test the forms and queries after migration because some data types, queries, or application logic may need changes.
Are SharePoint lists a good replacement for a high-volume Access backend?
SharePoint lists have limitations that can make them unsuitable for high-volume Access applications. For a larger or distributed deployment, evaluate SQL Server or another client/server database instead.




