Kbase P100330: Row leave trigger in the editable browse puts cursor in the wrong place
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/24/2005 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.x
Progress 9.x
Progress 8.x
SYMPTOM(s):
Row leave trigger in the editable browse puts the cursor in the wrong place
Upper row key puts the cursor 2 rows above the current position
The ROW-LEAVE code checks whether the user enter any data and if not the last row is deleted
CAUSE:
When the last row is deleted the browse widget applies row-leave from the last column that's why the cursor ends up 2 rows above the current position
FIX:
When the last row gets deleted end the ROW-LEAVE trigger with RETURN NO-APPLY.