Re: Separate buisness and display logic question

[Dennis <iseries@xxxxxxxxxxxx>]

If I understand the question and the code correctly, that capability would depend upon the validation routine(s) passing back enough information that its caller would know _what_ is wrong (as opposed to _something_ is wrong).

"David FOXWELL" <David.FOXWELL@xxxxxxxxx> wrote:

> Hi all, 
>
> A program displays 5 fields concerning a client's bank details. A
> procedure exists that accepts these details as a DS and checks each
> field. 
>
> eg:
>
>
> D CheckBankDetails...
> D                    PI       N
> D BankDetails                       likeds(refDS) const
> D error                             like(refError)
>
>
> /free
> 	If BankDetails.AccountNumber <> etc
> 		error = 'etc..'
> 		return *off
> 	endif
>
> 	If BankDetails.BankCode <> etc
> 		error = 'etc..'
> 		return *off
> 	endif
> /end-free
>
> Caller : IF not CheckBankDetails ( DSBank );
> 		//Now what?
> 	   Endif;
>
> On returning from this procedure, how can the display manager program
> position the cursor on the first incorrectly filled information using
> an indicator and DSPATR(PC)?
>
>
>
> Thanks.
>
>
> -- 
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing
> list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.

--  
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.