Field-by-Field enablement/disablement

[David Morrison]

Yes.   Use a temporary field for the label.  Then, you can highlight this field based on conditions.

ALIGN (,,5) (,,20)

FIELD t_label NOLABEL DISPLAY

FIELD t_entry-field NOLABEL

David Morrison
IT Department
858-450-1414 ext. 4211
From: powerh-l-bounces+dmorrison=mcbrideelectric.com at lists.sowder.com [mailto:powerh-l-bounces+dmorrison=mcbrideelectric.com at lists.sowder.com] On Behalf Of Penney, John
Sent: Tuesday, March 09, 2010 9:39 AM
To: power-l
Subject: Field-by-Field enablement/disablement

Dear PH Listers:

I have a challenge that I am going to poll the group for. I have a series of screens with fields that I wish to permit access to - or not - based on Application Security Class (ASC).

In and of itself that is no problem - a matchuser "X" in an input or edit procedure. What the management wants is for the screen to be able to "hilight" the fields that a User can access/change based on this ASC. I've tried the obvious "hilite if..." on FIELD statements, but all that does is highlight the data field itself. I want to be able to highlight the ID and./or LABEL of the field(s) in question. So that it's quite obvious to the User what he or she can, or cannot, change.

Aside from maintaining two (or more) separate screen source modules, I am stumped.

Does anybody have any ideas I could possibly entertain?

Thanks in advance....

John M Penney
1532 Fern Street SW
Olympia, WA  98502

(360)789-8159


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20100309/58f6678a/attachment.htm