Security Question

[ScottB]

Background
I have created an inventory database on my computers hard drive that
different people will be using. Two people, including myself, need t
have full database access. I only want the other 3 people to be abl
to input records and not modify the design of any database objects

Ideally, I want these 3 users to logon from any computer on th
network using thier Windows User ID and Passwords and be able t
access the database on a shared network drive. When they log int
the database, would like to grant them viewing and data entr
priveledges only

I tried using the Security wizard in Access 2003 and placed my Window
User Name and password in the Admin group. I closed out of th
database and reopened it. I then tried to modify the design of
form and was denied permissions. Fortunately I restored a backup.
know database Security is an involved topic but??

[b:eab2f4037f]My Questions are:[/b:eab2f4037f

1. Is there a simpler way than above to accomplish my objective
2. Am I close to accomplishing what I need but am missing some simpl
step
3. Or do I need an estensive explanation of database and networ
security to do what I want to do and if so can someone refer me to
good resource

Thanks

ScottB :

 

[Albert D.Kallal]

The 'normal' way to use ms-access in a multi-user environment is to split
your database.

Thus, you get a application part (forms, code etc.), this is called the
front end. This part is placed on EACH pc.

The back end part, or data only part is then placed on the drive share.

Further, you can create what is a called a mde version of this FE. This mde
has all of the code and design abilities taken away. In fact, a mde is
designed to be distributed to your users, and your uses will NOT be able to
modify the design.

Another thing you should consider is hiding all of the ms-access interface.
Again, you don't need security, or even any code to do this. (all of the
settings you need are in the tools->startup)

Try downloading and running the 3rd example here:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

(the ms-access interface hidden one)

Note how when you run this application, NONE of the ms-access interface
shows. Further, if you make the application a mde, and disable the shift-by
pass, you got a nice setup that should keep MOST users out of the
application and design side. You can find a shift-key enabler/disable here:

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html


And, if you want to polish your application off even more, take a quick
look at the following screen shots of ms-access, and note again how all of
the ms-access side is hidden....
http://www.members.shaw.ca/AlbertKallal/Articles/UseAbility/UserFriendly.htm

 

[Joseph Meehan]

Background:
I have created an inventory database on my computers hard drive that 5
different people will be using. Two people, including myself, need to
have full database access. I only want the other 3 people to be able
to input records and not modify the design of any database objects.

Ideally, I want these 3 users to logon from any computer on the
network using thier Windows User ID and Passwords and be able to
access the database on a shared network drive. When they log into
the database, would like to grant them viewing and data entry
priveledges only.

I tried using the Security wizard in Access 2003 and placed my Windows
User Name and password in the Admin group. I closed out of the
database and reopened it. I then tried to modify the design of a
form and was denied permissions. Fortunately I restored a backup. I
know database Security is an involved topic but???

[b:eab2f4037f]My Questions are:[/b:eab2f4037f]

1. Is there a simpler way than above to accomplish my objective?
2. Am I close to accomplishing what I need but am missing some simple
step.
3. Or do I need an estensive explanation of database and network
security to do what I want to do and if so can someone refer me to a
good resource?

Thanks,

ScottB

Access Security is not simple.

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 easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

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

 

[Joan Wild]

Background:
I have created an inventory database on my computers hard drive that 5
different people will be using. Two people, including myself, need to
have full database access. I only want the other 3 people to be able
to input records and not modify the design of any database objects.

Ideally, I want these 3 users to logon from any computer on the
network using thier Windows User ID and Passwords and be able to
access the database on a shared network drive. When they log into
the database, would like to grant them viewing and data entry
priveledges only.

Since you have only two levels of security required, you can implement
security such that these three people will not need to login to the mdb at
all. You should split the mdb, putting the backend (tables/relationships)
on the server. Give each user a copy of the frontend (all other objects) on
their computer.

I tried using the Security wizard in Access 2003 and placed my Windows
User Name and password in the Admin group. I closed out of the
database and reopened it.

You should have closed out of Access, and then used the desktop shortcut
created to open your secure mdb. For you and the second person, you will
use the desktop shortcut to open the secure mdb. During the wizard, it
offers you the option of giving permissions to the Users Group. Instead of
assigning permissions to any of the groups offered by the wizard, just
assign the permissions you want for the other 3 people to the Users Group.
This way you can distribute the secure frontend to them and they won't need
to log in.

Also consider making a mde from your mdb, and locking down the frontend.
Create custom toolbars, a startup form, look at the settings in Tools,
Startup, etc.