User Level Security - How to Remove?

  • Thread starter Peter van der Goes
  • Start date

P

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.
 
Ad

Advertisements

G

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
 
P

Peter van der Goes

Steve Huff said:
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.
 
P

Peter van der Goes

Steve Huff said:
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.
 
L

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.
 
Ad

Advertisements

Joined
Oct 13, 2014
Messages
1
Reaction score
0
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!
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

User-level Security 5
User Level Security 5
User Level Security 6
User security level 1
User-Level Security 5
user-level security 2
Collapse of User-Level Security!! 6
Scope of User Level Security 8

Top