[Bulk] Field-by-Field enablement/disablement

[Ken Langendock]

Oh baby that sucks.

The only way I know of doing this is to create a whole bunch of fields that
contain the labels and add the hilite IF option to them.

 

Ken

 

From: powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com
[mailto:powerh-l-bounces+ken.langendock=rogers.com at lists.sowder.com] On
Behalf Of Penney, John
Sent: March 9, 2010 12:39 PM
To: power-l
Subject: [Bulk] 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

 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2730 - Release Date: 03/08/10
02:34:00

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