Read-Only permissions make database read-only to others

[Atchleykl]

I have a database on a server. Only 3 people have write access to the
database, everyone else has read-only access. Unfortunately anytime a person
with read-only access opens the database, the whole database becomes
read-only and the write users can't do anything even if it is completely
unrelated to what the read-only person is looking at. Is there a way around
this? Thanks in advance!

 

[Gina Whipp]

Atchleykl,

Sounds like they are all using the same front end which would be expected
behavior AND can cause corruption issues. I would suggest you split the
database and give each user their own front end.

 

[david]

No, the only normal way around that is to implement Access 'user'
security, and give the read-only people read permission using
Access (workgroup) security.

The problem is that your read-only users have to write their read-locks
to the lock database (the ldb file). If they can't do that, Access has
no way of knowing if they are in the middle of a read, so it won't let
other users write -- writing in the middle of a read could cause the
read-only users to read inconsistent data, and Access won't let that
happen.

(david)

 

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

welcome to a classic Jet _BUG_.

Jet doesn't really support multiple users.
If you want to do this, you need to move to SQL Server.

With SQL Server, multiple people can write tables / queries at the
same time.

With Jet, it's not possible.

-Aaron