Partial read-only access

  • Thread starter Thread starter Pow
  • Start date Start date
P

Pow

Hello

At work, we use a Windows 2000 server, with about 45 staff networked
together.

One of the departments use an Access database that I designed. The
situation now is we want the rest of the company to use the same database.
However, we want to restrict the majority to read-only access, to prevent
any record deletion, changing of details etc. Only a limited few should
have full access.

Does anyone have any suggestions, or point me to websites that can, as to
how I can achieve this?

Most grateful for your help.
 
Pow

Get a copy of Garry Robinson's 'Real World Microsoft Access Database Protection and Security'. It will explain, in detail, how to do what you need to do plus a lot more. It has everything you need to know about proctection and security for Access applications packed into its 500 pages.
 
Generally the most straight forward way of doing this is, if
you have not already done so, to split your application into
Front End (Forms, queries, code, reports) and Back End
(tables).

Make two versions of the FE one where you set the forms to
prohibit alteration or addition of data through the form
properties and the other being normal 'full'
editing/addition and so on.

Then link the BE tables to each FE, you should seriously
consider code in the FE to look after linking if you don't
already have same.

Check out the sites listed here;
http://www.alphacos.co.uk/html/msaccess_tips.htm
 
You could create two frontends for each group, but that is difficult to
administer if you're making a lot of changes.

You could also implement user level security. Follow the steps in the
security FAQ

http://support.microsoft.com/?id=207793

Be sure to follow every step outlined or your database won't be secure.
 
You know, that really is simple now you've explained it! I don't often use
Access so when I do use it, I forget the basics!

I am very grateful to you.

Thanks
 
I know of one organization that simply made a Windows group which had read
only access to the share/folder on the server. This isn't the greatest
solution but is quick and dirty if you need something in a pinch.
Users opening the database will get a message saying that the database is
read-only and can get annoying.
 
I know of one organization that simply made a Windows group which had
read-only access to the share/folder on the server. This isn't the
read-only and can get annoying.

also, read-only users won't be able to use the database
while read/write users are in it.

(david)
 
Back
Top