Re: field level security - (Was Use of a trigger...? ....)

Rob,

Really!?   Did you try query? SQL?

Is there another way to implement FLS other than opsnav?  I've not had a
lot of experience with opsnav.  can you limit read authority first, before
the box is greyed out?

If this limitation is "working as designed", what's the point?  it seems to
me, the whole implementation is flawed.  what good does it do you if you
can't secure read authority?  Maybe this is why I've never seen or heard of
FLS being used.  too many limitations and quirks.

Has anyone on the list used field level security?
what are your experiences?

rick

--- original message ---
<snip>

Then I went into Operations Navigator and changed the security on FLD3 to
exclude the public.  When it came up I right clicked on the database and
selected permissions, clicked on details, clicked on columns.  There are
the following columns and there status:
Management - off
Alter - off - greyed out
Reference - off
Read - on - greyed out!
Add - on - greyed out!
Update - on
On FLD3 I turned update off.
Signed on as a peon.  They can see FLD3.  If they do UPDDTA then they can
see FLD3, they can change it but if they try to enter and save they get a
few messages, one of them being Not authorized to field FLD3 of file
RICHARD.  They can change other fields.

How do I secure read when the SOB is greyed out?