Forms 3.0 Required Field Attribute Q

 Hi.  

Does anyone know if there are any differences in the validation of a field
(forms 3.0) between the Required attribute when originally defined in the
designer, and the Required attribute set for a field using the SET_FIELD packaged procedure.

My situation is this. I have a field which I initially define as being required, but in order to get my list of values to work correctly on a different field, I have to use the SET_FIELD packaged procedure to turn off the required attribute.

(SET_FIELD (fieldname, required, attr_off); to be specific. I then turn
the field back on when I exit from my list of values block. (I know the required attribute is being set back on, I've checked.)

When I run the form not using the key-listval trigger, and I try to leave the record without filling in a value, I get a "FRM-40202: Field must be Entered." message. If I first use the key-listval trigger, I do not get the error message. This puzzles me.

Has anyone else run across this before?

Does anyone have a workaround?

Is this the way it is supposed to work?

One workaround I tried (unsuccessfully) was to put a key-nxtfld trigger on the required field, like the following:

enter;
check_package_failure;
next_field;

but when I do this, it does not acknowledge the on-validate-field trigger as being fired.

Now, I'm just dazed and confused :-/

Any ideas anyone?

As usual, you're help in this is appreciated ahead of time.

Bob Walters bobwal_at_infocom.com

Florists' Mutual Insurance Co. Received on Wed Dec 13 1995 - 00:00:00 CET