Results 1 to 5 of 5
  1. #1
    5 Star Lounger
    Join Date
    Mar 2001
    Posts
    989
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Splitting & Security (2003)

    Hopefully a straight-forward question.. Should a database be split first and security set up on both databases, or can security be set up and then split the database? Thanks, Andy.

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

    Re: Splitting & Security (2003)

    You can do either. If you split first, I'd recommend using the same .mdw file for the frontend and backend. If you secure first, then split, that will be automatic.

  3. #3
    5 Star Lounger
    Join Date
    Mar 2001
    Posts
    989
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Splitting & Security (2003)

    Thank you. I assume that if you allow someone to edit data via a form, then they also need permission to edit the query (and table(s)) that source the form? This would seem to be logical..? Andy.

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

    Re: Splitting & Security (2003)

    If the form is based on a table, they will need to have sufficient permissions on the table.
    If the form is based on a query, they will need to have sufficient permissions on the query. Permissions on the underlying table(s) can be granted to the users, or you can specify that the query runs with the permissions of the query's owner (RWOP=Run With Owner Permissions).
    See Frequently Asked Questions About Microsoft Access Security, in particular section 10.

  5. #5
    5 Star Lounger
    Join Date
    Mar 2001
    Posts
    989
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Splitting & Security (2003)

    Thank you once again.

Posting Permissions

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