Kbase P101400: VALUE-CHANGED Event in a BROWSE does not fire after a REPOSITION
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/02/2006 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
Windows
SYMPTOM(s):
VALUE-CHANGED event does not fire when using REPOSITION statement
Using BROWSE widget
VALUE-CHANGED event did fire with REPOSITION in versions lower than Progress 9.
CHANGE:
Upgraded from Progress 8.3x
CAUSE:
In Progress 8.3x, using REPOSITION did cause the VALUE-CHANGED event to fire. However, this behaviour in itself was caused by a bug which was fixed in Progress 9. Therefore, the correct behaviour is for the VALUE-CHANGED event not to fire when REPOSITION-ing. The VALUE-CHANGED event will fire for user-interaction such as a mouse or keyboard action.
FIX:
To fire the VALUE-CHANGED event after a REPOSITION, use something similar to the following:
REPOSITION {&browse-name} TO ROWID (<rowid>).
APPLY "VALUE-CHANGED" TO {&browse-name}.