Re: User security for ~120 organizations

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jack MacDonald (no email)
Date: 10/05/04 

Date: Tue, 05 Oct 2004 14:55:56 GMT

This is an appropriate use for User Level Security, but I would
proceed manually, rather than using the Security Wizard. See
http://www.geocities.com/jacksonmacd/ for my paper on user level
security plus links to other resources.

You will need to modify your database in order to filter the
information for each of the 120 organizations. The essential steps
will be to:
- add a field for holding the name of the appropriate user
- use the CurrentUser() function to determine the name of the current
user
- populate the field in the tables with the value of CurrentUser()
when you create records
- use CurrentUser() in your queries to restrict the records that are
displayed to the user.

In addition, you may want to explore Read With Owners Permission
(RWOP) queries that can be used to deny anybody the ability to read
the native tables, but to ONLY see the data by using your predefined
queries (which will use the CurrentUser() function). See the security
FAQ for additional information.

On Mon, 4 Oct 2004 13:23:03 -0700, Melvis
<Melvis@discussions.microsoft.com> wrote:

>Hello,
>
>I have only ever toyed with user level security once. I have been asked to
>make a database where each of about 120 organizations has their own password,
>and only one person from that organization can be in the database at a time.
>
>Also, they do not want each organization to see data from other
>organizations. Should I try this with the user-level security wizard? My
>experiences with this wizard have not been positive (i.e. the only one who
>had to enter a password to get into the database was me).
>
>Any help on this subject would be GREATLY appreciated.
>
>Thanks,
>~MATT

Relevant Pages

  • Re: open exclusive for back end design
    ... >> password but i would like to secure the be with user level security.I ... you can open the backend and set the password. ... > frontend, and delete the links. ... > If you want to implement user level security on the backend, ...
    (microsoft.public.access.security)
  • Re: A2007 Security
    ... enable the ShiftKey ByPass on my database? ... Create the bypass key property using the DDL argument so that only an ... administrator can change the setting (assumes you have set up user level ... security in A2000 prevented them from opening the tables or queries ...
    (comp.databases.ms-access)
  • Re: open exclusive for back end design
    ... you can open the backend and set the password. ... frontend, and delete the links. ... If you want to implement user level security on the backend, ... Follow the steps outlined in the security FAQ. ...
    (microsoft.public.access.security)
  • Re: User Levels ?
    ... Keep in mind if your using user level security in ms-access, ... As mentioned you would replace the security group "DeleteInvoice" with the ... access 2007 (it still works if you use the mdb format, ...
    (microsoft.public.access.formscoding)
  • Re: User permissions that actually work!
    ... I see from an earlier post you are using the security wizard. ... Implementing Access User Level Security (ULS) *IS* a complicated process ... Although the wizard is a very useful tool, ...
    (microsoft.public.access.forms)