Users and Passwords

[EmmaR]

This is probably a really easy thing to do but I need to set up users and passwords to access a database that will contain sensitive information so cannot be accessible to everyone.

Can someone please tell me an easy step-by-step way on how to do this, with multiple users allowed to add and edit information (but not the workings of tables, queries etc)?

I am pretty much self taught so nothing too technical if possible!!

Also, the user's name needs to be input into an "Entered By" field in a form automatically depending on who has logged in when a new record is created.

Thanks in advance for your help with this.

Emma

 

[Darth Vodka]

not that easy at all

Access 2003?

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

you need to:-
1) create a workgroup
2) create the users in the workgroup
3) block out "Admin" and "Users" permissions
4) create a secure db through the workgroup

to create a field in a table with the user's name in is easier, just make a form for them to update the table and set the default to their windows login

you can get the network login with some VBA like

NetworkID = CreateObject("Wscript.Network").UserName

 

[gemma-the-husky]

but its still very hard to allow users to use tables without being able to get at the database window - i dont think using workgroup security will prevent direct access on its own

 

[Sum Guy]

Emma:

DO NOT ENTER THE DARK WATERS AND UNCHARTED TERRITORY OF ACCESS SECURITY WITHOUT A DETAILED STEP BY STEP GUIDE.

I have been doing Access security for almost 10 years and I still have my guide with me when I do security.

I would recommend:

http://www.geocities.com/jacksonmacd
download the first file – Security Paper by Jack Macdonald. It’s a little long but it tells you everything you need to know.

 

[The_Doc_Man]

Search this forum also. I have authored a few threads on details of securing a database.

Use the forum search option for "Securing" and "Workgroup" as starting points for your searches.

The point made about special care for Admin and User is very important. Pay attention to it.

Be SURE beyond any and all doubt that you create a COPY with a different file name for the primary workgroup file. DO NOT USE SYSTEM.MDW as a workgroup name. (Has to do with the "default" nature of SYSTEM.MDW as a nasty way to sneak around any securing that you happen to do.

Also search for the "Command Line" options as a way so that you could create an iconic shortcut to your database that includes the -wkgrp option as a way to specify the correct workgroup to join in the first place.

 

[David Eagar]

Just an add on - if you are planning to upgrade to Access 2007 at some stage, all of the above may be obsolete - workgroups don't exist in 2007.

So before setting out on the hazardous journey of workgroup administration (and it is hard) plot your future and plan accordingly