Allowing R/O users access

[Gary T via AccessMonster.com]

I have a couple of lulus here but I'll address the other one in "Queries".

This one pertains to allowing users with read-only access to use the database
whilst a person with admin access is using it. The way it stands right now,
if an admin user is in it the r/o user gets a prompt that the DB is locked.

Bear in mind, I am only allowed to use system security, NOT Access security.

Any takers

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200602/1

[Rick Brandt]

Gary T via AccessMonster.com wrote:

I have a couple of lulus here but I'll address the other one in
"Queries".

This one pertains to allowing users with read-only access to use the
database whilst a person with admin access is using it. The way it
stands right now, if an admin user is in it the r/o user gets a
prompt that the DB is locked.

Bear in mind, I am only allowed to use system security, NOT Access
security.

Any takers

You cannot use file/folder permissions to provide read only access unless
you want ALL users to have read only access. For a mixed bag of permissions
you have to implement User Level Security.

By the way, you should see the inverse as well. When a read only user opens
the file first, a person who would ordinarily have full access will not be
able to get anything but read only access until all read only users exit.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Gary T via AccessMonster.com]

Rick Brandt wrote:

I have a couple of lulus here but I'll address the other one in
"Queries".

[quoted text clipped - 8 lines]

Any takers?

You cannot use file/folder permissions to provide read only access unless
you want ALL users to have read only access. For a mixed bag of permissions
you have to implement User Level Security.

By the way, you should see the inverse as well. When a read only user opens
the file first, a person who would ordinarily have full access will not be
able to get anything but read only access until all read only users exit.

My error.... User Level Security is being used.

A R/O user being in the DB first doesn't seem to affect admin users...

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200602/1

[Rick Brandt]

Gary T via AccessMonster.com wrote:

Rick Brandt wrote:

I have a couple of lulus here but I'll address the other one in
"Queries".

[quoted text clipped - 8 lines]

Any takers?

You cannot use file/folder permissions to provide read only access
unless you want ALL users to have read only access. For a mixed bag
of permissions you have to implement User Level Security.

By the way, you should see the inverse as well. When a read only
user opens the file first, a person who would ordinarily have full
access will not be able to get anything but read only access until
all read only users exit.

My error.... User Level Security is being used.

A R/O user being in the DB first doesn't seem to affect admin users...

Do R/O users have full access to the folder? All users need file create,
file modify, and file delete permissions on the folder for Access to be able
to properly manage the lcocking file.

When a R/O user opens a file already opened by someone with edit permissions
the LDB file needs to be modified to reflect the new user. If they have no
permission to modify the LDB file then they cannot get into your app.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com