User Level Security - How to Remove?

[Peter van der Goes]

I'm setting up a demo for students.
I want to show them how to apply user level security to a database (that's
the easy part), then remove it if necessary.
Once a Workgroup Information File has been created for a given database, is
there a way to disassociate the database from the Workgroup Information File
and return the database/application to its previous state (IOW restore the
ability to simply open the .mdb file by double-clicking on it instead of
going through the desktop icon created un the Security Wizard process.
If it's not possible to "go back", I need to know that as well.
Thanks in advance for any insights.

 

[Guest]

Once a database is created under a workgroup file it is "owned" by that
workgroup file. If you open up the user and or generic Admin accounts it
will work freely with other workgroups - but you will notice odd things like
viewing owner will say "unknown".

The best way to remove security and only way to disassociate it from it's
workgroup is was created under is to open up the generic Admin group to have
full rights, make sure you are joined to the generic workgroup that came with
Access, create a new MDB and import all the objects over from the previously
secured database.

--Steve Huff

 

[Peter van der Goes]

Once a database is created under a workgroup file it is "owned" by that
workgroup file. If you open up the user and or generic Admin accounts it
will work freely with other workgroups - but you will notice odd things like
viewing owner will say "unknown".

The best way to remove security and only way to disassociate it from it's
workgroup is was created under is to open up the generic Admin group to have
full rights, make sure you are joined to the generic workgroup that came with
Access, create a new MDB and import all the objects over from the previously
secured database.

--Steve Huff

Thanks very much, Steve. I was afraid it was something like that.

 

[Peter van der Goes]

Once a database is created under a workgroup file it is "owned" by that
workgroup file. If you open up the user and or generic Admin accounts it
will work freely with other workgroups - but you will notice odd things like
viewing owner will say "unknown".

The best way to remove security and only way to disassociate it from it's
workgroup is was created under is to open up the generic Admin group to have
full rights, make sure you are joined to the generic workgroup that came with
Access, create a new MDB and import all the objects over from the previously
secured database.

--Steve Huff

Dunno why, but my 12/2 response never showed up, so here it is again.

Thanks very much, Steve. I was afraid it was something like that.

 

[Lynn Trapp]

You can take the following steps to desecure a database.

1. Log on as a member of the Admins group.
2. Give the Users Group full permissions to all objects in the database.
3. Add the Admin user back into the Admins group.
4. Blank out the Admin User's password.
5. Join the default system.mdw file using the workgroup administrator.

 

[jswest]

1. Log on as a member of the Admins group.
2. Give the Users Group full permissions to all objects in the database.
3. Add the Admin user back into the Admins group.
4. Blank out the Admin User's password.
5. Join the default system.mdw file using the workgroup administrator.

--
Lynn Trapp

=========================================
Great worked for me with opening up Access 2000 DB in Access 2007. Thanks!