Re: EDIT Methodologies

John Carr wrote:
 
> Subject: Edit Methodologies

> Has anyone seen or used the following technique for this purpose?
snip, snip
>             DO
> 
>   XXCODE    IFNE 'B'
>             MOVE 'Y'    @ERROR
>             LEAVE
>             ENDIF
snip, snip
>             ENDDO
> *

This is the exact method I threw out for potential flames which started
the latest discussion of structured programming.  the only real
negatives given for the technique was the same as you stated: it didn't
show all errors in one pass.

I believe that showing all errors is <more> a coders preference than a
users preference.  If the user is good enough to make all corrections on
one pass thru the error messages, then they probably won't make more
than one or two mistakes in the first place.  If they aren't that good,
my contention is that they would then fix one at a time and press enter
until no more errors existed.  If the screen is designed well, and all
pre-requesite fields are placed before their dependents, and the error
messages are well written, (and, again, the user isn't on slow modem
connection), I don't believe it is an issue whether display one or all
messages at the same time.   
Most users will fix one and press enter to see the next, rather than
cursor down to the error subfile and hit the shift and roll keys.

IMHO of course.

Regards, 

Rick
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *