Re: FW: Keyword on DSPF entry field

["Richard B Baird" <rbaird@xxxxxxxxxxxxxxxxxxxxx>]

Nelson,

I think the reason you haven't gotten a reply is that you're probably SOL.

What it comes down to is good user training.  and good edit routines.

not even CSRINPONLY keyword will keep them from cursoring out of a numeric
field.  it will only make it advance across space to the next input field.

Sorry I couldn't help,

Rick
----original message----
C'mon, guys.  This is a real production problem we have, and I've had no
responses from anyone, yet.

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.

> -----Original Message-----
> From:   Smith, Nelson [SMTP:NSmith@lincare.com]
> Sent:   Monday, April 08, 2002 12:36 PM
> To:     rpg400-l@midrange.com
> Subject:     Keyword on DSPF entry field
>
> With a Check(FE) on a numeric entry field, field exit is required UNLESS
> the
> user presses one of the cursor control keys, like the tab or the arrow
> keys.
> This results in an unjustified field entry whenever there is already a
> number in the field. i.e. entering a 1 (in the first position of a field
> that already contains 0000001, and then doing a tab out of the field, the
> resulting field value becomes 1000001.
> This only occurs when the field already has a value and you enter a new
> value and then instead of a field exit, you tab or arrow out of the field
> and then press enter.
>
> Does anyone know how to prevent this anomaly? Or, is there anyway to
> disable
> the tab and arrow keys?
>