Re: How to set up security on a Network

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Debbie,

You'll need to implement User level security. There is a lot to it, so
study up and practice on a copy of your database until you're confident.

Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

Although the whitepaper is old, it contains information to help you
understand security.

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm

You won't want to have users repeatedly entering their username/password for
each form/report. Rather have them login once to the database (on open),
and then you can limit what they see based on their username or based on the
security groups they are members of.

Study up on the resources and come back with specifc questions.

--
Joan Wild
Microsoft Access MVP

Debbie wrote:
> I have no clue how to do this at all - here's what I'm trying to
> accomplish -
>
> I need to set up levels of security for multiple people over a
> network.
>
> Each person will access their own form and report but will not be
> able to access any others. (i.e. they click on their name on the
> switchboard and I want them to be prompted for a user name and
> password to open that particular form or report).
>
> Sounds simple enough but I'm clueless. So far the help I've been
> receiving with this database has been great in this forum!! So
> kudo's to all that have helped me!!
>
> Deb.


.

Relevant Pages

  • Re: Create a Form Password
    ... Let me provide my *few* thoughts about Access Security. ... Security in an Access database can probably be broken down ... into two big categories: home-grown security or Access ... User Level Security is using ...
    (microsoft.public.access.forms)
  • Re: Security Issues When Using Code in Access Reports
    ... design permissions on form/reports and everyone else (normally the user ... Conversely you could also create a simple report MDE, ... the data which would solve most of this without the Access security model. ... > prevent modification to database objects... ...
    (microsoft.public.access.reports)
  • Re: setting a password on a button on the switchboard
    ... Let me provide my *few* thoughts about Access Security. ... Security in an Access database can probably be broken down into two big categories: ... User Level Security. ... What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • Re: access 2003
    ... security in access 2003. ... The data will go on the server and the program database ... than the alternative of creating an mde file. ... MDW file from the written record. ...
    (microsoft.public.access.conversion)