Re: Multiple Databases - One Workgroup
- From: "Joan Wild" <jwild@xxxxxxxxxxxxxxxx>
- Date: Wed, 9 Nov 2005 15:30:56 -0500
CrystalJim wrote:
>
> Here is what I did: (not on the first try though - stumbled several
> times trying to get it all sync'd up)
>
> 1. Created a database "SecurityDB", that was connected to the
> system.mdw.
Databases are NOT connected to a mdw. I hope what you mean is that you
created a database SecurityDB.mdb while using the standard system.mdw (with
no login). Actually I don't see why you need to create this mdb at all.
> 2. In the "SecurityDB" database, created the company-wide
> securitygroup mdw file. Saved as "CompanySecurityGroup.mdw" in
> network folder.
Again, it doesn't matter what database you have open (in fact you don't need
one open at all). I assume you used the workgroup administrator to create a
mdw named CompanySecurityGroup.mdw.
> 3. Created a password for the admin user, added a new user - NewAdmin
> - added new user to the Admins group, and removed the admin user from
> the Admins group. Closed DB.
Nope. You were still using system.mdw. You should have joined your new mdw
file; closed Access and reopened it. To be certain you are using the
correct mdw, hit Ctrl-G and type
?dbengine.systemdb
It should return the full path to CompanySecurityGroup.mdw
Then create a password for the Admin user, create a new user - NewAdmin and
put them in the Admins Group, and remove Admin from Admins Group.
> 4. Logged on as the NewAdmin and created a password. Closed DB.
You don't need any DB open to do this.
> 5. Logged on as NewAdmin using new password.
And opened your unsecured mdb, right?
> 6. Using the Wizard, selected all groups assigning IDs to each group.
> No permissions for user-group. Added one new user - Newuser1 with
> password and PID (not default) - and placed in admins group.
> Verified NewAdmin was also in Admins group. Closed DB
> 7. Removed Security from database - "OlderDB" - that had its own mdw
> file by: a. Logging on as OlderDBAdmin
Well how did you logon? Perhaps at this point your are still joined to
CompanySecurityGroup.mdw. You'd need to use a desktop shortcut to open
OlderDB....
"path to msaccess.exe" "path to OlderDB" /wrkgrp "path to secure.mdw"
secure.mdw is the workgroup that OlderDB was secured with!
> b. Gave the users group full permissions on all objects
> c. Gave the Admin user full permissions
Not necessary
> d. Put admin user back in admins group
Not necessary
> e. Removed admin password
Not necessary
> f. Rejoined system.mdw
> g. Closed database
And Access. Then start Access, and...
> 8. Next, I created a new database "ImportOlderDB", connected to the
> system.mdw and imported all of the objects from the "OlderDB".
> 10. Joined the "CompanySecurityGroup.mdw". Closed DB
And Access. Then start Access and...
> 11. Logged on as NewAdmin (using password) created in step 3.
> 12. Now the issues start
> a. The "ImportOlderDB" Owner is the Admin user and cannot be changed.
Correct. It is now in a unsecured state. At this point you are using
CompanySecurityGroup.mdw. You can run the wizard with this mdb open and go
through the steps of securing it (choose to modify existing mdw).
I think you should do things in the following order.
Unsecure all your secure mdb files. You log in to each one using the
appropriate mdw file (you don't have to 'join' the workgroup, just use a
desktop shortcut as shown above) and then...
Grant all permissions on all objects (don't forget the database object) to
the Users Group.
Close them.
Open Access, and verify you are joined to the standard system.mdw workgroup
(no login) by hitting Ctrl-G and typing
?dbengine.systemdb
If it doesn't return the path to system.mdw, then use the workgroup
administrator to join system.mdw (close Access and reopen it and verify).
For each of your 'secure' mdb files, create a new database and import all
objects from them.
At this point you have a bunch of unsecured mdb files - as though they'd
never been secured before!
Open Access, and use the workgroup administrator to create a new workgroup
CompanySecurityGroup.mdw.
Now you can create a desktop shortcut with the following as the target....
"path to msaccess.exe" /wrkgrp "path to CompanySecurityGroup.mdw"
Double click the target and go to Tools, Security, Accounts and create a
password for the Admin user, create a new user - NewAdmin and put them in
the Admins Group, and remove Admin from Admins Group.
Close Access. Double-click your shortcut and login as NewAdmin. Set a
password for this user, if one doesn't exist yet.
Now open each of your unsecured mdb files and run the security wizard
(choosing to modify the existing workgroup; and create desktop shortcuts).
--
Joan Wild
Microsoft Access MVP
.
- References:
- Re: Multiple Databases - One Workgroup
- From: Joan Wild
- Re: Multiple Databases - One Workgroup
- From: Joan Wild
- Re: Multiple Databases - One Workgroup
- From: CrystalJim
- Re: Multiple Databases - One Workgroup
- Prev by Date: Re: Multiple Databases - One Workgroup
- Next by Date: How do checking Win2000 Password
- Previous by thread: Re: Multiple Databases - One Workgroup
- Next by thread: Disabling Certain Menu Items According to User Group
- Index(es):
Relevant Pages
|
