How do I disable the "Exclusive access" messages

[Prime76]

Hi,

I am trying to find out the best way to disable the following message that users receive when trying to access the db while other are logged in:

"You do not have exclusive access to the database at this time. If you need to make changes, you may not be able to save them later."

There are multiple users making changes and/or viewing the database at all times so the 20+ error messages that appear with the above verbiage can be quite annoying. By the way this database is set up with a front and back end so that they may be backed up monthly.

I'd appreciate any help

 

[gemma-the-husky]

if another user is in the database, or you have a form or query open, you cant change tables etc.

thats what it is telling you.

---------
i assume you are trying to change something in the backend - you do have to get evrryone out to do that, i'm afraid

 

[Prime76]

It's not necessarily that I need to make any changes to the db, it's that there are multiple users entering invoice information within different departments and when they go to login this error message appears. Once it is gone they can conduct their data entry as usual but i was wondering what would be a good manner to turn off this notification.

 

[boblarson]

If you don't want that message to come up, then you need to configure your frontend correctly. The correct configuration is to NOT share a single mdb/accdb/mde/accde file on the network, but to provide each user with a copy of the frontend on their machine.

 

[Prime76]

Yea...I was hoping that there was something that could be tweaked in the code to prevent the messages from appearing but if there isn't than I guess copying the front ends will do. The only problem is when I need to make some updates or enchancements to the front end, all the users would need to make a fresh copy of it and discard their old one. That is where some issues may arise.

Thanks for your help bob and husky.

 

[georgedwilkinson]

Why not just use Bob's free front end manager thingy at http://www.btabdevelopment.com?

 

[boblarson]

From another recent post with a similar problem:

1. Split the database to a frontend/backend.
2. Figure out how to initially distribute the frontend to the users. You can choose to have them put it in a common file path (like C:\YourPath) or let them put it where they may.
3. You could then use my Frontend Auto Update Enabling tool to enable auto updating on the frontend. So, what would happen is this -
a. You put the master mdb file on the network in a shared drive accessible to everyone.
b. After enabling that mdb file for auto updating, you distribute the initial file to your users.
c. After distributing, you then can make any changes necessary to your frontend in the master location and change the version number in two tables (one in the frontend and one in the frontend that is linked to the table in the backend).
d. The next time your users open their frontend, the program checks to see if the version numbers match. If they do not, then the db will let the user know that their frontend is out of date, it will close, delete the old file, copy the new frontend from the master location on the network, and automatically reopen for the user.

Then, you never have to distribute again. All you have to do is just worry about making the changes to the frontend master.

You can find my Frontend Auto Update Enabling Tool here:
http://www.btabdevelopment.com/main/MyFreeAccessTools/tabid/78/Default.aspx

 

[Prime76]

That utility will work great, Thanks Bob!