Re: EDIT Methodologies

John,

In a message dated 97-06-06 00:57:39 EDT, you write:

> I personally like going though Every edit and HighLighting, or Reverse
>  Imaging all fields on the screen that are in error so that the user will 
>  see all fields that are in error at once.   

Me too!

>  However sometimes there is a need to "Bail Out" or "LEAVE"  the edit
routine
>  upon finding the first error.   
>  
>  Has anyone seen or used the following technique for this purpose? 

We do this all the time (or approximate it in the AS/Set CASE tool).  We
usually have four levels of errors:  1)  A fatal error that needs to message
*SYSOPR and ends the program; 2)  A top-level error for which it would be
useless to validate dependent data (e.g., it's foolish to validate a ship-to
number if the customer number was invalid); 3)  The flow-through errors you
discussed; 4)  Warnings (sometimes requiring an F-Key, password, or signature
override).

>  The technique being; using a DO statement in conjunction with the LEAVE
>  opcode.  (No goto's or Cab's, Right?)
<<snip>>

Bravo!

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"In America, anyone can become President.  That's one of the risks you take."
-- Adlai Stephenson
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *