Access 2010 you do not have exclusive access to the database at this time

[psamu]

I would appreciate if any one can help. I have created a access database, it is shared, and saved in our network folder. But if second user open the database, get message "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later," If press OK many times it open the database. Thanks

 

[HiTechCoach]

With Access 2007 and later it has got a lot pickier about how you share a database.

The proper way is to split the database onto a apfront ned (application) and back end (data), Each user will have their own copy of the front end application. The back end (data) is shared. This will prevent the exclusiove issue you are having.


See: Splitting your Access database into application and data

 

[psamu]

With Access 2007 and later it has got a lot pickier about how you share a database.

The proper way is to split the database onto a apfront ned (application) and back end (data), Each user will have their own copy of the front end application. The back end (data) is shared. This will prevent the exclusiove issue you are having.


See: Splitting your Access database into application and data

Thank you so much.

 

[psamu]

With Access 2007 and later it has got a lot pickier about how you share a database.

The proper way is to split the database onto a apfront ned (application) and back end (data), Each user will have their own copy of the front end application. The back end (data) is shared. This will prevent the exclusiove issue you are having.


See: Splitting your Access database into application and data

If I split the database, can I keep the front system in the network? Then create a shortcut on the desktop? Or it has to be in the local drive, then create a shortcut on the desktop? I have several users. Thanks

 

[Joe4]

The best way is to give each user their own copy of the front-end to run off of their computer.

What I typically do is place a copy of the front-end database on the network, and then create a batch file which copies the front-end off of the network to their computer, and then opens that copy. Then I just put a shortcut to the batch file on their desktop. That makes it really easy to push out updates too (just replace the copy on the network, and the next time they open the database via the batch file, they will get the new version).

 

[psamu]

The best way is to give each user their own copy of the front-end to run off of their computer.

What I typically do is place a copy of the front-end database on the network, and then create a batch file which copies the front-end off of the network to their computer, and then opens that copy. Then I just put a shortcut to the batch file on their desktop. That makes it really easy to push out updates too (just replace the copy on the network, and the next time they open the database via the batch file, they will get the new version).

Thanks. What is batch file means? Copy of front-end. ?

 

[Joe4]

A batch file is a simple exectuable that runs a bunch of DOS commands automatically when clicked. You can create one using any Text Editor (i.e. NotePad, WordPad), and if you name it with a ".bat" extension, it will run automatically open clicking it. Here is a good link on it here: How to Write a Batch File (with Examples) - wikiHow

Here is a link to an example of one that does what I described: Is splitting the DB the correct choice?
You obviously would have to alter it to match your file paths and database names.

There is also a good link on splitting here: Splitting your Access database into application and data

 

[HiTechCoach]

If I split the database, can I keep the front system in the network? Then create a shortcut on the desktop? Or it has to be in the local drive, then create a shortcut on the desktop? I have several users. Thanks

Your issues are caused by multiple people having the same database opened at a the same time.

The key to why a split database works in your case is that the front end (app) is NOT shared. This eliminates the issue you are experiencing. The back end can be shared because it is "Linked" but not opened directly with Access.

Some alternatives to deploying updates:

A great way to deploy updates automatically that also always users to pin the database to the task bar, which does happen, is to use the FRONT-END AUTO-UPDATE ENABLING TOOL (Works for all versions 2000 and up) found here: Free Access Tools | BTAB Development

Here is another great tool: Application Starter

 

[psamu]

A batch file is a simple exectuable that runs a bunch of DOS commands automatically when clicked. You can create one using any Text Editor (i.e. NotePad, WordPad), and if you name it with a ".bat" extension, it will run automatically open clicking it. Here is a good link on it here: How to Write a Batch File (with Examples) - wikiHow

Here is a link to an example of one that does what I described: Is splitting the DB the correct choice?
You obviously would have to alter it to match your file paths and database names.

There is also a good link on splitting here: Splitting your Access database into application and data

Thank you