Security

[Guest]

I have built a database for my company...works great, just need good
user-level security. Where can I find some easy to follow and thorough
literature on how to set up this security? The database is located on our
company intranet, don't know if that makes matters worse. I need security
where everyone can view the info, but not edit or add any. I will then have
a few amount of logons that can alter and add data. Question-can more than
one person log under the same name? This would make it easy having just two
logons-one that doesn't need a password or logon (universal user) for
read-only, and one that gives access to editing and adding data that these
few people could use simultaneously. Any help or references is appreciated.

 

[Rick B]

Check out the following links...



Security FAQ

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



The Security Whitepaper is also worth reading to help you understand.

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



Joan Wild:

www.jmwild.com/AccessSecurity.htm



Lynn Trapp

http://www.ltcomputerdesigns.com/Security.htm

I have built a database for my company...works great, just need good
user-level security. Where can I find some easy to follow and thorough
literature on how to set up this security? The database is located on our
company intranet, don't know if that makes matters worse. I need security
where everyone can view the info, but not edit or add any. I will then have
a few amount of logons that can alter and add data. Question-can more than
one person log under the same name? This would make it easy having just two
logons-one that doesn't need a password or logon (universal user) for
read-only, and one that gives access to editing and adding data that these
few people could use simultaneously. Any help or references is

appreciated.

 

[Joseph Meehan]

I have built a database for my company...works great, just need good
user-level security. Where can I find some easy to follow and thorough
literature on how to set up this security?

There is no easy to follow user level security instructions. It is not
easy, at least the first few times.

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 database is located on our
company intranet, don't know if that makes matters worse. I need security
where everyone can view the info, but not edit or add any. I will then
have
a few amount of logons that can alter and add data. Question-can more
than
one person log under the same name? This would make it easy having just
two
logons-one that doesn't need a password or logon (universal user) for
read-only, and one that gives access to editing and adding data that these
few people could use simultaneously. Any help or references is
appreciated.

There is a non-user level password protection that may do what you want
without user level security. However please read on.

To use user level security, you must authorize full access to the folder
or directory where the database resides. That means anyone with any access
can delete the whole thing. You need to have a good backup plan in place if
the information is important.

Also consider just putting a copy out there so they can play with it and
keep the real one somewhere safe, just copying it out there as needed, like
after updates.

I don't know how many users you may have on at one time, but with many
users or even a few users using it a lot, you want to use a split database
with the data on the server and each user having their own front end with
static tables (those that don't change), queries, forms and reports on their
own machines linked to the table on the server for the dynamic data. Safer
and faster.

If you have users on the one and only copy you have and need to make
changes, that can prove to be very frustrating, since you need to get them
off before you can make design changes. That is why you would not want them
all under the same name and password anyway. BTW, they get to choose their
own password when they log on the first time, you never know what it is.
You can reset it to blank if you like, but you can't change it so something
else. Of course you can also just lock them out.

Good Luck