DSPF numeric field editing

["Timothy Adair" <tadair@xxxxxxxxxxxxxxxx>]

I've searched the archives but have been unable to find any previous 
reference to this issue.

I have a DSPF with a numeric field (11,4) where the user is allowed to key 
in a number with or without a decimal point.  If they key in a decimal 
point, then the program takes that number as the actual value.  If not, then 
the program assumes 4 decimal places and divides the entered number by 
10,000.  (Please don't ask why - I've fought that battle and lost.  Yes our 
users are still in the dark ages.)

So far, so good.

Let's say they key in the number "2" and press Enter.  The program will 
assume four decimal places and divide by 10,000.

So far, still good.

If there are no errors or messages, the program will go back to the first 
screen and allow the user to select another record to be updated.  But if 
there is an error or message (my message, not system message) the program 
loops around and does another EXFMT and the number shows up exactly as they 
keyed it in, ignoring any editing, even though the value is correct (0.0002, 
verified in Debug).  I've tried an edit code and an edit word - neither 
works.

Is there some kind of quirk with a numeric display field that ignores any 
editing if there's an ERRMSG on?

Here is the field DDS:

A            FUTPRC        11Y 4B 14 28COMP(GE .0000)
A                                      DSPATR(PC)
A                                      EDTWRD('0      .    ')
A  41                                  ERRMSG('Price Below Cost.  Press F5-
A                                       to override.' 41)
A  42                                  ERRMSG('No Cost Available' 42)
A  49                                  ERRMSG('Both fields are required' 4-
A                                      9)
A  40                                  ERRMSG('Abnormal price - press ENTE-
A                                      R to accept.')
A  40                                  COLOR(RED)


Please help...  I now have a dent in my wall, and a headache.

TIA,

Tim