Open in Shared/Exclusive question

[kbrooks]

I just read a post recently about going into Tools/Options/Advanced and making sure the db was set to open as shared. It was NOT, so I set it to shared. My (dumb) question is this....do I have to go to each individual user's computer, open the db, and set it to shared?

The reason I ask......previously, we would get an error occassionally that the db could not be opened because it was opened exclusively by user x. I thought changing it to shared would solve this problem but it hasn't.

A couple other things worth mentioning.....
* I only today split it into a front end/backend
* The users have a shortcut on their desktop that points to the front end (previously the entire db, until I split it today) that resides on a network folder. Do I need to copy it directly to their PC?

TIA

 

[The_Doc_Man]

The ability to open a database in Exclusive mode is one of the rights controlled through WorkGroup security. If you aren't implementing this type of security, you will have trouble.

Basically, if you force everyone to go through a workgroup, you can set their account privileges to allow shared but not exclusive access. Make sure you retain Open Exclusive rights so you can do maintenance.

Search this forum for the "security" keyword and the "Exclusive" keyword. We have had several recent threads discussing the issue of shared/exclusive access rights.

 

[Pat Hartman]

Your code is fighting with itself. You have some code that is trying to update the current record and that is causing the conflict.