When working with User Level Security, is it normal for the
owner of a database to *not* be able to change the ownership
of the database object?

--
Thanks,
croy

Yes (assuming you mean via the security dialogs). You normally change
the owner of the database object, by creating a new mdb while logged in
as the user you want to own the database.

If you need to change the owner, you'd create the new database, and then
import all the objects from your old database. The permissions won't
travel with the import, so you'd use a utility such as Jeff Conrad's to
transfer the permissions...
http://www.accessmvp.com/SDaigle/index.htm

Joan Wild
MS Access MVP

croy wrote:
> When working with User Level Security, is it normal for the
> owner of a database to *not* be able to change the ownership
> of the database object?
>

On Mon, 05 Jan 2009 19:31:13 -0500, Joan Wild
<(E-Mail Removed)> wrote:

>Yes (assuming you mean via the security dialogs). You normally change
>the owner of the database object, by creating a new mdb while logged in
>as the user you want to own the database.
>
>If you need to change the owner, you'd create the new database, and then
>import all the objects from your old database.

By "you'd", you mean the prospective new owner, right?

> The permissions won't
>travel with the import, so you'd use a utility such as Jeff Conrad's to
>transfer the permissions...
> http://www.accessmvp.com/SDaigle/index.htm


Thanks Joan. Another keeper!

croy wrote:
> On Mon, 05 Jan 2009 19:31:13 -0500, Joan Wild
> <(E-Mail Removed)> wrote:
>
>> Yes (assuming you mean via the security dialogs). You normally change
>> the owner of the database object, by creating a new mdb while logged in
>> as the user you want to own the database.
>>
>> If you need to change the owner, you'd create the new database, and then
>> import all the objects from your old database.
>
> By "you'd", you mean the prospective new owner, right?

Yes

Joan Wild
MS Access MVP