Razzak, I am sorry I did not make myself clear. The EEP is on the table exit level. I just want to know if there is a better way to program the EEP so there will be no chance of the form locking up if more than one field was empty.
I do have EEPs in each of the fields mentioned but the entry person can bypass them with a click to other fields. The On Exit (from the table) EEP is a double check, so to speak. Again this is the EEP in question: IF vShipState <> vSgetState THEN PAUSE 2 USING 'Shipstate & C# State must be the same!' CAPTION + ' New Order ' ICON STOP ' SKIP TO vShipstate RETURN ENDIF IF vPromocat IS NULL THEN PAUSE 2 USING 'You MUST Select Catagory!' CAPTION ' New Order ' + ICON STOP SKIP TO Promocat RETURN ENDIF IF vPromoID IS NULL THEN PAUSE 2 USING 'You MUST Select PromoID!' CAPTION ' New Order ' + ICON STOP SKIP TO PromoID RETURN ENDIF -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Wednesday, October 14, 2009 8:53 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: checking information before leaving table At 09:35 AM 10/14/2009, Jim Belisle wrote: >I am sure there is a better way to program this since I may run into a >situation where more than one field may be blank. In your specific situation, validate your record using the "On Row Exit" EEP at the table level. Here's how: Form Designer | Main Menu | Tables | Add/Remove Tables ... Main Table | Table Settings ... Table Settings | On Row Exit EEP Very Best R:egards, Razzak.
