Re: Different FE's for different users

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



When there is user-level security I have used group membership to show or hide controls, etc. In a form's Load event I may have something such as:

If Not UserGroup("Admins") Then
Me.cmdSecurity.Visible = False
Else
Me.cmdSecurity.Visible = True
End If

The database uses a startup form that includes the command button cmdSecurity, which opens a form that includes toolbars and other information used to administer database security, but it could have been any form. The users who are not a member of the Admins group don't see the command button.

"ant1983" <ant1983@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:49817355-FCB8-44D1-9670-A95BF8F235E2@xxxxxxxxxxxxxxxx
Hi,

Not sure if this is under the correct topic - If not, apologies...

My database (a BE and the copies of the FE on each user's computer) will
soon be live in my client's enviroment.

I would like to know the following:

I would like different FE's on certain user's machines - What is the best
way to do this.

Some context: I would like the director of the company to be able to have
access to all menu's and to be able to have unlimited restrictions in terms
of editing etc.

I would further like for the clerks to only have limited access and editing
restrictions.

How would i proceed with this?

Many thanks for assistance!!

Wayne

.



Relevant Pages

  • Re: Different versions of Access
    ... I just saw that "splitting a database" was an entirely different reason from ... implementing User-Level Security. ... that some posters want/expect to modify a database ... How do you separate program testing from live data? ...
    (microsoft.public.access.security)
  • Re: Protect Front and Backends
    ... the database file is split into a front end and back end. ... User-level security can be adequate for many situations. ... > How do I protect a backend? ...
    (microsoft.public.access.security)
  • Re: Relink question
    ... if you use user-level security then I recommend you read the ... Graham Mandeno ... so Access won't let me implicitly declare. ... there is no law that says an Access database must have the extension ...
    (microsoft.public.access.formscoding)
  • Re: Is UserLevel Security Really Necessary?
    ... With user-level security, you would give the user no permissions to write to ... location of the SQL database they could work around it. ... Immediate Window, as well. ...
    (comp.databases.ms-access)
  • Re: Login Permissions
    ... I know this isn't the most secure thing. ... >You need to use the built in access User-Level Security. ... >> I have created a database for our Financial Departments ... My initial setup was using a logon box for the ...
    (microsoft.public.access.forms)