How can I remove security from Access 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I had turned on the security for Access 2000 before converting my database
application to Access 2003. Now the owner shows as <unknown> instead of
administrator. Which does not allow me to take ownership and make the
changes necessary to the data.

Hopefully someone out there can help.

Randy
 
Hi, Randy.

You'll need to join the workgroup that was used to secure the database.
Select the Tools menu -> Security -> Workgroup Administrator to open the
Workgroup Administrator dialog window. Select the "Join" button and then
navigate to the workgroup information file (*.MDW) that was originally used
to secure the database.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Gunny,
Tried it, makes no difference. although my user ID is shown as a member of
the admin group as well as all other groups just for drill, I am not able to
take ownership or change permissions.

The owner shows as <unknown>. When I look at the security for the file it
shows my user id has full control and ownership.

Randy
 
Hi, Randy.
The owner shows as <unknown>. When I look at the security for the file it
shows my user id has full control and ownership.
Click to expand...

If I understand this correctly, then your User ID owns all the objects in
the database, but doesn't actually own the database itself.

When one looks at the database owner in the User And Group Permissions
dialog window and the <Current Database> object lists <Unknown> as the
current owner, it means that the current workgroup file was not used to
secure this database file. If you are positive that you have joined the
correct workgroup, then I can only think of three scenarios for this
phenomenon to occur.

1.) You've converted the secured database from an earlier version of Access
to the current version of Access, and were logged in as the owner of the
original database, but the conversion didn't go smoothly. Microsoft
recommends removing user-level security prior to conversion to the current
version, then reapplying user-level security to the newly converted
database.

2.) Someone has created another workgroup file, joined it, then created a
brand new database and imported all of the objects from your "secure"
database into the new database, then changed the ownership of all objects to
your User ID. You would now be using this new database, not the database
you created, secured and converted earlier. This is obviously a lot of
steps, so can't be accidental.

3.) The database file is corrupted.

Sounds like the first scenario is the most likely for your case. If I were
you, I'd go back to the Access 2K version, remove security, then convert it
to Access 2003, then reapply security.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top