Preventing Truncation of Decimal and Floating Point Fields

The precision used when converting and storing data entered by the user is controlled by the picture string for the field. For example, if you specify the picture "#####@##", nothing prevents the user from entering "123.4567". When the user leaves the field and the field entry is validated, the entry will be stored and redisplayed in the field as " 123.45".

Truncation of the user's entry when necessary is the default. To prevent such truncation problems, you can do one of two things:

• nTurn the CHKTRUNCATE field option ON for the field. When enabled, the user's entry is checked to ensure that truncation does not occur. If truncation will occur with the number as entered, an error message is displayed, and the user is prompted to remove the extra decimal places.
  
  
• nSpecify a "safe" picture string for the decimal field. If using the RTENTRY field option, specify a hard decimal separator in the picture. Do not use a soft decimal character in the picture.

  For entering numbers in scientific notation, specify the full precision picture based on the maximum value of a single or double floating point number for your compiler. Refer to your compiler's documentation. A recommended picture for full precision entry of scientific notation in a double-precision float field is "99.99999999E9999". If you do not use a full picture for exponential notation, specify a range of values that can be entered.