Read Only permission to folder where database resides

[Guest]

We have an Access database stored in a network folder, we then have a number
of users with full permissions to this folder and some users with read-only
permissions. At present a user with read-only permissions only seems to be
able to open the database when no-one else has it open. If they do manage to
open it (i.e. no-one else in it at time) then it locks the file and non of
the other users can access it. If the file is already in use when a
read-only user tries to open it they get an Access error message "Can not
Lock File" Anyone any ideas. Weve tried the database using Access 2000 and
Access 2003.

TIA
Ally.

 

[Joseph Meehan]

We have an Access database stored in a network folder, we then have a number
of users with full permissions to this folder and some users with read-only
permissions. At present a user with read-only permissions only seems to be
able to open the database when no-one else has it open. If they do manage
to open it (i.e. no-one else in it at time) then it locks the file and non
of the other users can access it. If the file is already in use when a
read-only user tries to open it they get an Access error message "Can not
Lock File" Anyone any ideas. Weve tried the database using Access 2000 and
Access 2003.

TIA
Ally.

For things to work well, they need read, write, create and delete
access.

BTW is that a back-end database with front-end databases on the user's
machines? If not, I suggest you consider splitting the database so you have
that arrangement. It tends to work much safer and generally faster.

 

[gandalf]

if the user can't create the .ldb file the database will
be opened in exclusive mode

you will need to give them create/read/write/delete/change
permission.

 

[Guest]

What's the best way of going about making the data read-only for specific
users?

I do usually split the front end from the back, but not in this case as it
started out as a single user database but seems to have grown.

Ally.

 

[Joseph Meehan]

What's the best way of going about making the data read-only for specific
users?

The best way is user level security. Learning to use it is a very steep
learning curve, but it is a great tool. Easy for the user and you, once YOU
learn your part. The user does not need to do much.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can lock
everyone including God out.

Practice on some copies to make sure you know what you are doing.

The alternative is Access password protection. It is much less secure
and less versatile, but it does work. For that the built in help file works
fine. However I do recommend making a copy of the database before you start
messing with it anyway.

I do usually split the front end from the back, but not in this case as it
started out as a single user database but seems to have grown.

Yea, I know how that goes.

User level security can work either way.