Is there any way (field attribute, key word, etc.) to keep the beloved end user from not using the field exit key when entering a value in a numeric field ?? We have users who will continually use the tab key or just hit enter when entering a 1 (for example) in a field, thereby creating a value of 100 million, 1 billion, etc. My associate and I have searched for a solution, but with no luck.
Thanks, Bill
Software/Hardware used:
ASKED:
June 30, 2006 11:38 AM
UPDATED:
July 10, 2006 7:38 AM
we had this problem and we implemented a very nice solution, but our solution requires very much work on your part.
We removed all numeric fields from screens and replaced with character fields. We then have a service program that validates, parses and re-formats the character field into a nice, viewable field.
The result is very, very nice. Very user friendly. And, resolves the problem that you stated. It also resolves the problem where users want to enter a currency symbol or commas into the number. There is more overhead, but such a solution works very, very well.
There is a field-level DDS keyword that may help:
CHGINPDFT(FE)
Requires the user to press a Field Exit key to leave the field.
You could also use the field attribute CHECK(RZ). These will right adjust the field and replace with leading zeros regardless of how the field is exited. If the user types a 1 in a 5 byte numeric field, instead of it being interpreted as 10000 it is interpreted as 00001.
Quick answer is use the Mnadatory Field Exit (MF)keyword. Requires them to always use the field exit key even when entering data.
If you’re using Client access you want to remap the keyboard so they can get to field exit without using the shift key. Unless Field Exit + – are good enough.