Re: Separate buisness and display logic question

An interesting take on the idea of having a error data structure with
an indicator for each field, is to move from simple types to complex
types....

d AccountNumber_t ds TEMPLATE
d value 11s 0
d error n

d BankDetails ds qualified
d AccountNumber likeds(AccountNumber_t)

This also fits into my NULL handling (since RPG doesn't offer full null support)

d AccountNumber_t ds TEMPLATE
d value 11s 0
d error n
d null n

HTH,
Charles





On Wed, Feb 2, 2011 at 8:58 AM,
<J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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.

--
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.