Users Group - Database - Administer

[Larry Gordon]

I have been working with workgroup security since Early Access 2.0 and
thought I knew what I was doing, but I just hit a snag that is not that
important from a "I can't do that" point of view, but is extremely important
from a "I should know that" point of view.

Here is the situation.
I have a database that I have full security on. I have Larry that has
complete rights to everything and owns all the objects. For the sake of
argument I am only using one group, "Users". The following are my
questions.

Question #1
If I have a table, query, form or report that I give "Users" group
Administer rights on and then I send them the database without the secure
..mdw workgroup file,
I understand why the following is true
They open the database (they have rights to open) with the Accesses default
workgroup file (System.mdw) and they can do whatever they want including
changing the owner with those objects.

I don't understand the following:
However if they "Users" have Administer rights on the database
(when I am logged on as Larry using original Workgroup file - set security
in Tools/Security/Users & Group Permission).
When they log on using the default Workgroup , they cannot change the
security of the objects in the database or the Owner of the objects if the
objects themselves do not explicitly give them Administer rights on the
objects .
I don't understand. Why can't the change the owner or security on the
objects. (When I read security in code I see this is the situation, but I
don't understand why.)
dbSecDBAdmin = True
dbSecWriteSec = False
dbSecWriteOwner = False

Question #2
When I log on using the original Workgroup file, I can't change the owner of
the database (I'm the owner), but I can change the security or owner of any
other object in the database. Why is this the case?

Any help would be greatly appreciated.

Thanks
Larry G