Interesting user issue

[martinmike2]

Hello,

I have a custom workgroup file with users defined. Some of my users
are getting Exclusivity warnings when logging into the system while
others are not. I have had this app running with 10 people
simultaneously before employing the workgroup. What could be causing
this issue? I have my users opening the db via a shortcut that uses
the custom workgroup and runtime mode.

 

[Douglas J. Steele]

What's the exact message you're getting?

Exclusivity should have nothing to do with having applied User-Level
Security. It may, however, be related to NTFS permissions on the folder
where the database resides. All users, whether they can update the database
or not, should have a minimum of Create and Update on the folder where the
database resides. This is because Access wants to create a locking file
(.ldb) in that folder when the first user connects. As subsequent users
connect to the database, Access updates the locking file. It's usual to give
them Delete permission on the folder as well, because Access tries to delete
the locking file when the last user disconnects.

 

[JString]

This *might* not be your problem, but I would double check the permissions
you set for each user. 'Open Exclusive' under the 'Database' object type
should be disabled for standard users. Also, check the permissions for
'Admin' and 'Guest'. I usually take away ALL permissions for these two users
as this will force your users to log in using their personal user names.

 

[a a r o n . k e m p f]

JET is not reliable
It is not consistent

who the **** told you to use this piece of shit database?

Any programmer worth their beans moved to SQL Server a decade ago.

SO SORRY THAT YOU ARE HAVING RELIABILITY PROBLEMS.
MOVE TO A DATABASE WITH A FUTURE, THANKS

 

[a a r o n . k e m p f]

wow, that's neat-- so you have to deal with security in multiple
places; and yet it isn't 1/10th as secure as SQL Server
wow, that's neat-- so you have to deal with security in multiple
places; and yet it isn't 1/10th as secure as SQL Server
wow, that's neat-- so you have to deal with security in multiple
places; and yet it isn't 1/10th as secure as SQL Server
wow, that's neat-- so you have to deal with security in multiple
places; and yet it isn't 1/10th as secure as SQL Server
wow, that's neat-- so you have to deal with security in multiple
places; and yet it isn't 1/10th as secure as SQL Server

 

[Aaron Kempf knows nothing]

 

[Tony Toews [MVP]]

Aaron Kempf knows nothing

As much as I don't like Aaron and his postings I feel that your
postings are also very inappropriate. We should not be making fun of
someone else.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/