Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database security 1

Status
Not open for further replies.

Xzibit7

Technical User
Jun 20, 2006
172
0
0
US
I am trying to create a database with different usernames and passwords where people can log on. My problem is I have one table that I want only the admin and manager to be able to edit and the rest of the data everyone can have access to. Using the user account wizard does not enable me to do this. It allows me to restrict the one table but then wont let me input any other data to the other tables, or it doesnt restrict any data at all there is no in between.
 
Wow I think I need to start reading the posts below
 
Yes, You should.

There are many posts about this topic in this forum.

But for starters:

Code:
1 create a new workgroupfile (use WRKGADM.EXE). DO NOT NAME IT SYSTEM.MDW. If you use only one MDW then continue, else start WRKGADM.EXE again and switch back to the default system.mdw.
2 open access using this new workgroupfile (use a shortcut if needed see example)
3 open the database (file menu >> open) that you want to secure.
4 create a new user and add him to the admins group (this wil be the new administrator)
5 check that the admins group has rights to all objects in your DB!
6 change the default admins password from blank to something you will remeber.
7 remove all permisions from the users group in the database
8 close the database
9 reopen the database the database you are securing (use shortcut if needed!) and log in as  the new administrator
10 run the security wizzard on the new DB (saves time)
11 remove the (standard) Admin user from the admins group
12 create the users and groups your application needs
13 join your users to their rspective groups
14 assign the appropriate permissions to the groups
15 add or remove group permissions as needed.

You need a shortcut if you use several mdw's. If you're sure you will use only one mdw, than access wil always use the same mdw (as is set to default with WRKGADM.EXE) and you do not need a shortcut.
A shortcut example is: c:\program files\..\path to access.exe "path&filename of the database" /WRKGRP "pathname and filename of the newly created MDW file"

ALSO:
1) split the db in front end (no tables) end back end (only tables).
2) Make the backend network accesible
3) distribute the (compiled/mde) frontend to the users.
4) do not let users have direct accces to tables, use forms, queries etc.

EasyIT
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top