Results 1 to 5 of 5
  1. #1
    Star Lounger
    Join Date
    Aug 2002
    Location
    Wichita, Kansas, USA
    Posts
    71
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Table Security (Access 2000)

    I am working on a Human Resouces database, where the supervisors are going to input salary increases through a form. I have found a way for the supervisor to only see their employees through the form.

    My problem is how to protect the table itself. Even with security on the database they have to have update access to the table. If they know how to get to the tables, then they can view everyones information instead of just their own. Even if I put the tables in a separate database and use a link to them, don't they still have to have update access to the tables in the other database? So if users can figure out how to get to the other database they will still be able to look at everyones data through the table.

    I don't really want to create a separate table for each supervisor which is the only other though I've had.

    Any help will sure be appreciated! Thanks.

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Table Security (Access 2000)

    The Microsoft Access Security FAQ downloadable from MSKB article 165009 has some info on this.

  3. #3
    Star Lounger
    Join Date
    Aug 2002
    Location
    Wichita, Kansas, USA
    Posts
    71
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Table Security (Access 2000)

    Thank you so much Hans!!! I think this has all the info I need for now <img src=/S/thankyou.gif border=0 alt=thankyou width=40 height=15>

  4. #4
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Table Security (Access 2000)

    In particular you want to look at Question 10 in the document Hans pointed you to. You might also want to think about using either the MSDE or SQL Server for this kind of project. SQL Server provides a more robust way of managing people access to data using views and stored procedures, and is inherently more stable (less prone to corruption) than a Jet back-end.
    Wendell

  5. #5
    Star Lounger
    Join Date
    Aug 2002
    Location
    Wichita, Kansas, USA
    Posts
    71
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Table Security (Access 2000)

    Thanks Wendell! Question 10 is what helped me. I haven't done much through an SQL server so am not comfortable trying to work that way, but I agree it is probably the better way to go overall. Initially I didn't know this project was going to get this deep into user level security.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •