RE: FW: Keyword on DSPF entry field

Unfortunately, even if you use a character field and it already contains 200
for example in a 4 pos fld, and user types 100 and tab instead of field
plus, then the result to the program is still going to be 1000.  Very much a
PITA.  Sorry I could not offer any useful suggestion on getting around this,
just wanted to point out that the use of alpha field, while it may cut down
on some of this type of error, it is not fool proof.  I would agree with
another post that it is definitely a matter of user training and some
reasonableness error checking can be done

Joe Giusto II
Programmer/Analyst
Ritz Camera
Beltsville, MD


 -----Original Message-----
From:   rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]  On
Behalf Of Douglas Handy
Sent:   Tuesday, April 09, 2002 12:16 PM
To:     rpg400-l@midrange.com
Subject:        Re: FW: Keyword on DSPF entry field

Nelson,


>We need to be able to prevent users from tabbing or arrowing out of a
>numeric field without first doing a field exit.  There must be some
standard
>way of preventing this error.

I do have a standard way of preventing the error -- I don't use numeric
fields,
and gave up on them even back on the S/36.  Instead I use character fields
from
the program viewpoint, so that the WS controller and/or the OS service
routines
do not interpret the contents.

This lets me perform my own character to numeric conversions (in a service
program on the 400, it was monolithic standardized subroutine on the S/36),
and
handle left justified fields correctly and issue errors when there are
embedded
blanks.

Doug
_______________________________________________