Access security - permission checkboxes

[Amit]

MS Access 2000
=============
Hi,

I have a quick question regarding the permission checkboxes when
implementing security for Groups/Users.
The checkboxes that assign security to database objects have three options
when clicked:
1. clear
2. greyed out and checked
3. distinct checked (with a white background)

I've been searching like crazy on the Internet/MS Help for an explanation
for the "greyed out and checked" state, but I have failed to find an
explanation.

Can someone please shed some light on this?

Thanks.

-Amit

 

[Chris Mills]

Greyed out happens when you select more than one object (usually to set
permissions on multiple objects at the same time).

Greyed-out does not tell you what the permissions currently are (they could be
the same or different for the selected objects), you can't tell.

Clear or clear-checked means you have just cleared or set that permission for
those objects. Greyed means you haven't altered it in this session. Greyed is
always ticked even if none of the objects individual permissions are ticked (I
think), so the tick means nothing in this case.

Personally I never trust "greyed", unless I Cancel. I feel happier
setting/resetting all the checkboxes, if they are greyed and I alter them.

Chris

 

[Scott McDaniel]

If I follow you correctly, this indicates an Implicit permission ... in
other words, one not directly assigned to the particular User, but instead
one that is "inherited" through a User's membership in a particular Group.

 

[Chris Mills]

It sounds good but I'm afraid it doesn't (unless they changed it in A2k3).

It's easy enough to test, as I did before posting.

Chris

 

[Joan Wild]

If I follow you correctly, this indicates an Implicit permission ...
in other words, one not directly assigned to the particular User, but
instead one that is "inherited" through a User's membership in a
particular Group.

No it doesn't. Implicit permissions are not indicated at all in the dialog.

 

[Scott McDaniel]

Don't know what I was thinking ... seen that behavior somewhere, thought it
was on Access security but obviously not ... guess I should check before
posting!!