Re: Separate buisness and display logic question

That's ok, but for heaven's sake don't use *IN35. Name your indicator. It
will be one less thing for future generations to curse under their breath
about. :D


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



dmosley@xxxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/02/2011 09:58 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Separate buisness and display logic question






How about seperating the individual field validations, and then pass an
option indicator, that would be associate to the positioning indicator.

D @Check_BankDetails_AccountNumer...
D PI N
D inAcctId 6A value
D inAcctId_Ind * value options(*nopass)
*
D errIndicator s n based(inAcctId_Ind)


/free
if (inAcctId <> etc);
if (%parms() = 2);
inAcctId_Ind = *on;
endif;
return *off;
endif;
return *on;
/end-free

Caller : IF not @Check_BankDetails_AccountNumer( scrnAcctId: *in35);
//Now what?
Endif;

David L. Mosley, Jr.
Technical Solutions Architect
Dancik International, Ltd.
2000 CentreGreen Way, Suite 250
Cary, NC 27513

www.dancik.com



J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/02/2011 08:58 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Separate buisness and display logic question






Not. And neither can a web application use <fieldname>.focus() to position


the cursor. The only way to know which field to put the cursor on is that
CheckBankDetails indicates which field is in error. Either have an extra
parameter that specifies which field is in error or use an extra data
structure with a boolean for every field in the main data structure. Then
the checking routine can use 'Errors.Accountnumber = *ON' and the calling
routine can use 'if Errors.Accountnumber ....'.

Joep Beckeringh

David FOXWELL

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.