RE: How do I protect a SNGCHCFLD?

If a radio button selection works, wouldn't a single field of values 1, 2, 3 be equivalent? I don't see why you'd need to have the complication of multiple Y/N fields.
--
Sean Porterfield


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave
Sent: Wednesday, March 07, 2012 08:44
To: Midrange Systems Technical Discussion
Subject: Re: How do I protect a SNGCHCFLD?

Thanks Booth,
That's a technique that I haven't used and I'm not sure if I understand. If I create another format F2 and then write F1, EXFMT F2, what stops the user from placing the cursor in F1 that contains the SNGCHCFLD and changing it?

Secondly, the user can view the data but also choose to print a letter of acknowledgment by changing one other field on the screen, so it's not entirely protected.

At the moment I have 3 radio buttons. 1 = no choice, 2 = first choice, 3 = second choice.

It all works great except for the protected issue. I'm being given no time to look at this properly, so it looks like I will have to go back to ordinary B fields. I'll have 2 fields that can be Yes or No each, but only one yes and one no and at least one yes... And all the error messages that go with it.

Le 6 mars 2012 17:35, Booth Martin <booth@xxxxxxxxxxxx> a écrit :

You are protecting the entire screen, if I am understanding you correctly?

Instead of DSPATR(PR) on every input capable field, could you exfmt a
whole new format with only one hidden field that overlays the screen
you wish to protect? That way you don't need to use an indicator or
the
DSPATR(PR) at all, anywhere on the screen. You just write your
regular screen format and then exfmt the protecting format.

That should pretty much do what you need done, with a lot fewer lines
of code.


On 3/6/2012 8:34 AM, Dave wrote:

Hi all,

Was glad to get my radio buttons up and running at last but as I'm
using the same screen to enter and visualize data, I just bunged on
a

DSPATR(PR)

with an indicator as one usually does with any ordinary field. This

doesn't

compile. How do I prevent the user from modifying the choice when
visualising data?

Thanks

--
Booth Martin
802-461-5349
http://www.martinvt.com

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.