You cant view this objects permissions

  • Thread starter david epsom dot com dot au
  • Start date
D

david epsom dot com dot au

Is administer permission inherited?


If I log in as MyDev (who is a member of the Admins group), I can see that
the Users Group has admin permission on the database.

MyUser is a member of the Users Group.

But if I log in as MyUser, I can't see the permissions on the database
object: I get "you can't view this objects permissions ... you must have
administer permission for it"


I would have thought that since MyUser is a member of Users, and Users has
Admin permission on the database object, I should be able to see the
permissions for Users on the database object when I was logged in as MyUser.

Did I miss something?

(david)
 
J

Joan Wild

david said:
Is administer permission inherited?

If I log in as MyDev (who is a member of the Admins group), I can see
that the Users Group has admin permission on the database.

I assume you are just testing something, as the Users Group should not have
administer permission on the database object.
MyUser is a member of the Users Group.

But if I log in as MyUser, I can't see the permissions on the database
object: I get "you can't view this objects permissions ... you must
have administer permission for it"

In my testing this isn't so. I gave administer permission to the Users
Group for the database object. I logged in as a user and did not get that
message when viewing the permissions for the db object. When I tried to
change the permission for another object (that neither the user nor the
Users Group has administer permission on), I received a message that I
couldn't. In other words, it all worked as expected.
I would have thought that since MyUser is a member of Users, and
Users has Admin permission on the database object, I should be able
to see the permissions for Users on the database object when I was
logged in as MyUser.

True; and you'd be able to see/set the permissions for any user/group on
that object.
 
D

david epsom dot com dot au

Well that is very odd. I can view database permissions
if I put MyUser into Admins, but giving admin permission
to MyUser or to Users is having no effect. A2000,
using (probably) a converted A97 workgroup. Same result
with the user Admin. Perhaps some anomaly from using
a converted workgroup?
I assume you are just testing something, as the Users Group
should not have administer permission on the database object.

Checking the permissions :~) They got that way because of
management vanity.

Thank you for your response

David Graham
 
J

Joan Wild

david said:
Well that is very odd. I can view database permissions
if I put MyUser into Admins, but giving admin permission
to MyUser or to Users is having no effect. A2000,
using (probably) a converted A97 workgroup. Same result
with the user Admin. Perhaps some anomaly from using
a converted workgroup?

I can't comment on that, as I've never converted a workgroup (I can't see
why that would matter). I always unsecure, convert the mdb, and re-secure.
 
D

david epsom dot com dot au

Not an anomaly from using a converted workgroup or
file: the new workgroup has the same behaviour with
a new file.

MyUser, who in the new workgroup has personal admin
permission for the old database, can add users, add
users to groups, change database properties, and set
permissions for tables with admin permission, but cannot
view or set permissions for the database object.

Opening a new database (just created under a different
workgroup), MyUser has no personal admin permission,
but the Users group has admin permission. Again, MyUser
can do all admin tasks except viewing or setting permissions
for the database object.

Harking back to the information you provided earlier:
I logged in as a user and did not get that
message when viewing the permissions for the db object.

Note that I can view my own permissions: when logged
in as MyUser, I can see that MyUser has admin permission
on the database object, but can't change that (the
controls are disabled). The message appears when trying
to look at permissions for a group or another user.

Working with Access 2000 sp3. I guess the next thing to
do is try it under 2002/2003 to see if the behaviour is
different.

(david)
 
J

Joan Wild

david said:
Harking back to the information you provided earlier:


Note that I can view my own permissions: when logged
in as MyUser, I can see that MyUser has admin permission
on the database object, but can't change that (the
controls are disabled). The message appears when trying
to look at permissions for a group or another user.

I was able to change the permission for another group.user.
Working with Access 2000 sp3. I guess the next thing to
do is try it under 2002/2003 to see if the behaviour is
different.

Perhaps that's it. I was testing with Access 2002 (I don't have it
installed to test) - maybe you've found another instance of the problem with
Access 2000 (the UI doesn't jibe with actual settings). You could script
out the permissions and see what they say.
 
S

Scott

perhaps it is because the user account you are logging on with, even though
it has admin permissions, is not the owner ot the object. only the owner
(admin) by default can change certain properties?
 
J

Joan Wild

Scott said:
perhaps it is because the user account you are logging on with, even
though it has admin permissions, is not the owner ot the object. only
the owner (admin) by default can change certain properties?

A good thought, but you don't need to be the owner to change the
permissions.
 
D

david epsom dot com dot au

I just tried with Access XP, and the behaviour is different,
but still not what you see. I have not looked at the
scripted permissions yet.

In XP, with the same (A2K) file, when logged in as the owner,
a member of the Admins Group, I can see that the Users group
has admin permission on the database object. When logged in
as a member of only the Users group, I can see that the Users
group does NOT have admin permission!

(david)
 
J

Joan Wild

david said:
I just tried with Access XP, and the behaviour is different,
but still not what you see. I have not looked at the
scripted permissions yet.

In XP, with the same (A2K) file, when logged in as the owner,
a member of the Admins Group, I can see that the Users group
has admin permission on the database object. When logged in
as a member of only the Users group, I can see that the Users
group does NOT have admin permission!

I don't know what I did the other day, but am now getting the error you see.
It works OK for all other objects, but not the database object.
 

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

Top