How do I change object owner from "unknown" to admin?

[HB]

New to Access security. Created DB, then ran security wizard, I now can not
modify original objects (tables, queries, etc.) because the owner is
"unknown". What can I do? Thanks.

 

[Joan Wild]

New to Access security. Created DB, then ran security wizard, I now
can not modify original objects (tables, queries, etc.) because the
owner is "unknown". What can I do? Thanks.

You don't mention the version, but this is happening because you are using
the wrong workgroup to access the mdb. Recent wizards create a desktop
shortcut for you to launch your secure mdb. If you look in the properties
of the shortcut, you'll see the target line. It includes the wrkgrp switch
which specifies the correct workgroup to use for the session. All other
sessions (like opening via Windows Explorer) will use your default workgroup
file, and silently log you in as 'Admin', a user that doesn't have
permission to use your secure mdb (and rightly so). Use the desktop
shortcut instead.

 

[HB]

Sorry. v2003 and v2000 file format. And I'll try to explain the problem more
clearly. I'm not sure it has to do with my workgroup file.

The main problem is, after I ran the security wizard I now get a message
that says I do not have "Administer" rights to change the objects I created
before running the wizard, though I am logged in as admin. But if I create
an object (table, etc.) and check the owner, it says "Admin".

The second problems is, If I go into User/Group permissions and try to
change the object's owner, the owner says "unknown", and I can't chage it. I
imagine this problem will be solved when the first problem is solved.

This happens no matter which .mdw I am "joined" to, the default system, or
the new one I created.

Thanks for the help.

HB

 

[HB]

I didn't know about that...but it's there! Thanks.

But now I can't get into the file no matter what!

I did figure out a work around; create a new DB and import everything. But
I'm still confused as to what went wrong.

HB

 

[HB]

I thought logging in as "Admin" was the same as Administrator, which it
isn't. The Admin ID (which I thought Access created on its own) needs to
have explicit Administer authority. This was the problem.

If I log in as Administrator, all is solved.

 

[Joan Wild]

Sorry. v2003 and v2000 file format. And I'll try to explain the
problem more clearly. I'm not sure it has to do with my workgroup
file.

The main problem is, after I ran the security wizard I now get a
message that says I do not have "Administer" rights to change the
objects I created before running the wizard, though I am logged in as
admin. But if I create an object (table, etc.) and check the owner,
it says "Admin".

That means that you are not joined to the workgroup you used to secure it
with. Secondly, when you secure a mdb you remove all permissions for the
admin user, so you should not be logging in as this user. Of course any
object you create, you (admin) will own because you are logged in as that
user.

The second problems is, If I go into User/Group permissions and try to
change the object's owner, the owner says "unknown", and I can't
chage it. I imagine this problem will be solved when the first
problem is solved.

Again, you are not logged in using the correct workgroup file.

This happens no matter which .mdw I am "joined" to, the default
system, or the new one I created.

How are you 'joining' the workgroup, and how are you determining which one
you are using?

Are you prompted for a username/password when you open the mdb?

 

[Joan Wild]

I didn't know about that...but it's there! Thanks.

But now I can't get into the file no matter what!

I did figure out a work around; create a new DB and import
everything. But I'm still confused as to what went wrong.

Careful, that may not be what you really want to do. If you are still
logged in as Admin, then this user will own all the objects in the new mdb
(not something you want).

As for logging in using the shortcut - when you ran the wizard, you setup a
new user and optionally set a password for this user. If you set the
password, be aware that they are case sensitive (check your capslock key).
If you did not set a password, then login using the username and no
password.