Kbase P98127: SCREEN-VALUE of an empty value in a COMBO-BOX returns different results in Progress 9.1x and OpenEdg
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/01/2009 |
|
Status: Verified
SYMPTOM(s):
Same behavior with dynamic and static COMBO-BOX widgets
COMBO-BOX has an empty value i.e.
Dynamic:
LIST-ITEMS = ",Item 1,Item 2"
Static:
LIST-ITEMS "","Item 1","Item 2"
Progress 9.1x: SCREEN-VALUE returns an empty string after user-interaction
Progress 9.1x: SCREEN VALUE returns unknown (?) before user-interaction with the COMBO-BOX
OpenEdge 10.0x: SCREEN-VALUE always returns unknown (?)
Version 8 and OpenEdge 10.x behave the same
FACT(s) (Environment):
Progress 8.x
Progress 9.1x
OpenEdge 10.0x
All Supported Operating Systems
CAUSE:
Bug# OE00111431
CAUSE:
The behavior observed in Progress 8 and OpenEdge 10 has been deemed the expected behavior. The SCREEN-VALUE for an empty combo-box should always return the unknown value. If the version 9.1x behavior is desired a new startup parameter, -scrvalmode, has been introduced in 10.1A02, which reverts to the 9.1x behavior.
FIX:
Option #1
Upgrade to OpenEdge 10.1A02.
Use -scrvalmode 1 to return "" for the screen-value if the currently selected item is a blank item. Note that if no item is selected, the screen-value will still be unknown.
Another option, -scrvalmode 3, sets input-value to unknown if the screen-value is unknown (for combo-boxes only), in addition to providing the behavior of -scrvalmode 1.
Option #2
Use INPUT-VALUE in place of SCREEN-VALUE to workaround the problem and avoid the changes in the behavior between versions.
INPUT-VALUE returns an empty-string in both Progress 9.1x and OpenEdge 10.0x.