Exclusive Access error message

[psycoperl]

Hi all I am developing an application using MS Access 2010. We have our database and forms in two different files, they are both stored on our network drive.

When our users are trying to open a form to enter data (NOT make any modifications to the forms), they periodically get "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."

How can I resolve this and prevent it from happening? It happens if they are opening the same form or different forms.

Thanks

 

[Montez659]

It sounds like you are one step away from fixing it. You reference that you have your data and forms in two different files meaning the database is split. Good.

It also sounds like both these files are placed on a shared network drive to use. Not as good.

Better (and to solve your error) would be to have the back end of the db on the network drive and the front end loaded up onto each individuals workstation. Each user will have their own interface and should solve the error you are receiving.

Unless there is some other underlying error, I would assume this is the problem.

 

[psycoperl]

Is there an easy way to "Push" any updates to the front end database to each of the users or ensure that they are using the most recent version? As we roll out our application and expand the featureset that we are implementing, I would like to be able to ensure that the users in our office are using the same (most recent version) with the least amount of difficulty as each user can work at multiple machines depending on staffing and location.

 

[Montez659]

There are a probably a few different ways to do this. One would be to load up a .bak file (I think that is the right thing) to each computer that would automatically check for the latest version from a folder on ther server. I am very unfamiliar with how to do this, although a bit of research could probably help you out.

A way that I have been thinking of doing in theory (haven't implemented yet) is to have a table with version info on the back end and then a table on the front end that contains current version info (some might say this defeats the purpose of the split db, but it is only one table with one piece of info). If the version numbers do not match up, then when any form loads (based off off some VBA) I would hide all the controls and populate a mesage specifying they need to d/l the latest version from the server.

This last example is all in theory so I am not sure if it would work or not, but in my mind I don't see problems. I don't have IT access to the network which is why solution 1 wouldn't work for me.