Kbase P64218: Dyn: Errors when setting displayFormat of a dynLookup, to no
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/28/2004 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.1A
FACT(s) (Environment):
Progress 9.1D
SYMPTOM(s):
Progress 9.1D08
Dynamics 2.1A01
For a dynLookup, special character format in displayFormat property (such as '99' instead of 'X(n)')
** Character <char> at position <n> must be digit. (630)
** Data string <string> does not match format (629)
Unknown error code 2 for attribute INPUT-VALUE on the FILL-IN fiLookup. (4104)
StackTrace reads:
displayRecord adm2/datavis.p (d:\dyn21a\gui\adm2\datavis.r) at line 4920
displayFields adm2/viewer.p (d:\dyn21a\gui\adm2\viewer.r) at line 3721
--> displayLookup adm2/lookup.p (d:\dyn21a\gui\adm2\lookup.r) at line 5502
CAUSE:
Known issue due to a problem in the core when querying the INPUT-VALUE attribute.
These errors occur when displayLookup is call, and also when typing in the lookup leads to a SCREEN-VALUE that is not compliant with the FORMAT defined in displayFormat.
FIX:
If you want a character field do be handled like a numeric field, then you should better redefine the field as integer so a FORMAT like "9999" will be really effective. Then a lookup will not make any problem with it.