Using copy of existing workgroup file on a new db?

[geralf]

Hi all,

I've set up security on my database before with great success, and now I'd like to use the same workgroup file (a copy with a new name and location) to secure a nes db.

I open the new db, and join my earlier created mdw file. I'm prompted with that I have joined my workgroupfile.

I then set permissions for each user in the workgroupfile, remove admin rights for the admin user account, and assign admin rights to my own account. I am also the owner of thr db.

I now run the security wizard, and I make no changes to any checkboxes.

This goes nicely, and the wizard closes after making a backup file.

I now want to re-join the system.mdw file, so I don't get prompted with the logon dialog when opening a new db or an unsecured db.

If I now try to start my new secured db by double-clicking on the secured mdb file it opens ?????

Where am I going wrong?

Thanks in advance for any help.

 

[Pat Hartman]

I think there is a bug in the security wizard in some versions of Access that doesn't properly remove admin permissions.

Start again but this time follow the directions in the security FAQ step-by-step. The FAQ may have a shortcut fix so you can try reading the problems/resolutions also.

 

[geralf]

Hi Pat!

I'm very sorry for not to have responded to your post earlier. I had really forgotten about this one. I have not secured the database yet since I'm still developing it and are having other issues with the db. It will however be secured before starting to use it. An idea though - what if I make a copy of the secured db that uses the workgroup file I want to use. Delete all objects and import all objects from the unsecured db. (setting permissions for the new objects and changing the db name etc.) Would not that work as a workaround?

Thanks for your help Pat!

 

[Bat17]

Rather than delete from a copy just create a new db, while logged in to the secure workgroup, then set permissions. Really just the reverse of De-Securing a DB

Peter

 

[geralf]

Thanks Bat for your reply!

I tried to create a new database when I was logged into the secured database. It still opened when I double clicked the new ddatabase (when I was logged of the secured of course).

Thanks for your suggestion though.

 

[Bat17]

you need to create the new db after joining the secure workgroup. Then import the stuff over from the Unsecure db and set permmisions

You don't need to run the wizard either!!

Peter

 

[geralf]

Hi Peter!

Thanks for your reply.

I finally got the chance to try this, and it worked, EXCEPT that I actually had to run through the security wizard - not changing any options. Then it was secure.

Thanks for the help agaom!