Thats true, Mike, but if I want to verify the validity of the entered state
via my eep, I can't.
So, the question is, is this a bug or not ?
Thanks,
Jim
At 04:57 PM 8/18/04 -0500, you wrote:
>
>----- Original Message -----
>From: <[EMAIL PROTECTED]>
>To: "RBG7-L Mailing List" <[EMAIL PROTECTED]>
>Sent: Wednesday, August 18, 2004 4:14 PM
>Subject: [RBG7-L] - On Exit EEP problem
>
>
>> Hello All:
>> Can someone verify this bug -OR- is this a bug ??
>> Version 7.1.76 win
>>
>
>I can verify that what you say happens, but when I put Not Null
constraints on
>the custState field, I get the desired effect without the eep
>
>> If you have a form used for ADD (or enter), and you wish to do the error
>> checking at the field level (which I prefer), it appears that you cannot
>> have an eep on the last field, and have it validate correctly. If this is
>> something that was reported earlier, and I missed, please let me know.
>>
>> Very simple to replicate.
>> Create a form using comcomp (or any database), and only have two
>> fields....say company (field 1) and custstate (field2).
>> Then within the form, create a variable such as vstate text = custstate.
>> On the custstate field, use an on exit eep (to insure that the field is not
>> null), by inserting the following code:
>>
>> IF VSTATE IS NULL THEN
>> PAUSE 2 USING 'STATE IS MISSING'
>> SKIP TO CUSTSTATE
>> RETURN
>> ENDIF
>> RETURN
>>
>> Then, save the form.
>> Next, run the form and leave the custstate field blank.
>> The record gets added (with the blank state field), and THEN the field gets
>> checked for null, and you get the error message
>> What am I missing to make this work ?
>>
>> Jim.
>>
>
========================================
Jim Schmitt
Ohio Software Services
2211 Lake Club Drive
Columbus, Oh 43232
Phone 1-614-863-1850
Fax 1-614-863-0325
E-mail [EMAIL PROTECTED]
========================================
