I have code in an exit event of a field that is populated with a value. If the user blanks out the field I use a Case statement that examines the record status field. (values can be signed off, reassigned, assigned, etc) Once this field contains a value the user is NOT allowed to clear it. So I display a message within the Case statement indicating they must entered a value, they click OK and I set them in the field by using the uidoc.gotofield(AssignedTo). This work great if they click on another field but if they directly to the save button and click on it. The message box is displayed two times and I get lotus error msgs…cannot locate field…and the record is actually saved with blanks.
Subject: RE: using the Goto…Need HELP Quickly…thanks
I agree Andre!
With that said, inout validation formulas only go off when a form is refreshed (F9, onsave, etc.) Over and over and over again I find that other fields on the form - mainly computed fields (eg, audit trails, etc.) have conditions placed on them like IF something … and then every time someone go to save a doc and an input validation formula stops the save, other fields are unnecessarily computed anyway. To the point that I’ve just about given up on input validation event in favor of writing all validation code to a dedicated agent.
I know this sounds cynical, and it doesn’t apply to a form that one designs solely from scratch and can anticipate this issue - but any time I’m working an application someone else had before me, inout validations tend to be painful
Subject: RE: using the Goto…Need HELP Quickly…thanks
Agree with you Jon, I have moved most of my input validation stuff to querysave - its just alot easier when you need to validate richtext for example or validating based on ceartain conditions.
So it sounds like you are using the exiting event of the field to control this behavior. I usually don’t use this event for such requirements because its not failproof. A user can click another button (like save) or escape and this would not trigger the event.
I would probably move the code to querysave or close to handle this type of thing.