How to go from 2 secure MDB’s with 1 workgroup to 2 workgroups

I have two secure front-end databases (e.g. secureapp1.mdb & secureapp2.mdb)
that reside on each user’s desktop pc and one secure back-end database (e.g.
securedata.mdb) that resides on the server and is linked to the front-end
databases. All 3 database files were created and secured using the same
workgroup file (e.g. system.mdw) which also resides on the server in the same
folder with the back-end database.

My manager now wants to separate the user accounts for secureapp1.mdb &
secureapp2.mdb so that he has the flexibility to assign different user
permissions in each of the two applications. For example Joe Blow may have
admin permissions in secureapp1.mdb and no permissions in secureapp2.mdb

What is the best way to transition to dedicated workgroup files for each
front-end database without loosing my custom groups and corresponding
permissions?

I’ve tried using the User-Level Security Wizard to create a new workgroup
file for secureapp1.mdb however, when I do that I loose my custom groups and
permissions.

Any help would be greatly appreciated.

.

Relevant Pages

  • Re: Trying to program workgroup security using DAO... Help!!
    ... After you created a new workgroup file, you then created a new user to be a member of Admins. ... Here are the steps I've taken to secure a target database (which is ... Assigning permissions. ... Assigned all specific permissions to objects for the new groups I ...
    (microsoft.public.access.security)
  • Re: Becoming the Owner
    ... so you can open the database while joined to ... and check the permissions for the Database object type. ... remove the permissions on all objects for the Users group. ... workgroup file. ...
    (microsoft.public.access.security)
  • Re: Sorting out security
    ... Right now I am set up with a functional clean database, ... The default "admin" user is not the owner of any part of the ... database and has no permissions whatsoever. ... > The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
  • Re: Menu
    ... A database is not linked to a particular workgroup file. ... If my workgroup file has no password for Admin, ... because Admin should have no permissions to any ...
    (microsoft.public.access.security)
  • Re: Inconsistent ability to access database after "secured"
    ... If someone can open the database without using your secure workgroup file, ... Security -> User and Group Permissions... ... opens right up - no login and no permissions error. ...
    (microsoft.public.access.security)
Loading