opening an Access 2016 database in Shared mode

Question

I am trying to share an Access database on a network drive. I have checked the Client settings, and these are set to shared. Also all of the users have full control permissions to the folder on the network drive. What else should I look at? The database will not open for a second user. They get an error message stating that the first user has the database open in exclusive mode.

Answer 1

Hi,

you have to split your Db in a Front-End (Client) and a Back-End (server). 

In front-end links tables that are in back-end. In every pc you will have a front-end.

Ciao Mimmo

Answer 2

Hi Deborah,

As the query is related to Access database front end back end customization,  we suggest posting it in TechNet forum for dedicated support. It is a specific channel handling this kind of queries and questions.

Thanks for your understanding,

Tina

Answer 3

We tried splitting the database and that did not work either.

Another point I did not mention before is that this database has links to a list on our SharePoint 365 site.

Is there a way to make this work? I found another post related to Access databases giving the same error we are receiving here, and the user had to eliminate the SharePoint links to make the database accessible to multiple users. That is not a solution that will work for our application.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice\_access-mso\_winother-mso\_2013\_release/my-split-access-2013-database-gives-me-database/8249ef66-b7ae-43dc-85a8-f5e13e743a90

Answer 4

You don't share an Access database.  You need to split the database then place the BE in a centrally accessible location, relink the tables, then give every user their own copy of the FE.

See: http://www.devhut.net/2017/04/09/setting-up-an-ms-access-database/ for more details (well worth your time!).

Answer 5

As soon as the first user starts making design changes the database becomes exclusive. Mimmo gave you solid advice. Each user should have his own local front end with forms, reports, queries, etc. The back end should reside in a shared server folder and contain only the tables.

Many Access databases are never split, usually out of ignorance on the developer's part, and work fine for a while. But once users start making design changes, all comes crashing down. I wrote a rather extensive article on how to deploy and maintain a split database. You can find the article here