Kbase P161108: 4GL/ABL: A browse ROW-ENTRY event trigger does not fire when the browse ROW-ENTRY event occurs.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/03/2010 |
|
Status: Unverified
SYMPTOM(s):
4GL/ABL: A browse ROW-ENTRY event trigger does not fire when the browse ROW-ENTRY event occurs.
A browse ROW-ENTRY event trigger code fails to execute when the user enters a browse row.
A MESSAGE statement in the browse ROW-ENTRY event trigger code never executes when a browse row is entered by the user.
A browse ROW-ENTRY event trigger does not fire as evidenced by the failure of a MESSAGE statement to execute when a user enters a browse row.
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CAUSE:
The browse ROW-ENTRY event trigger did not fire because a duplicate browse ROW-ENTRY event trigger was defined later in the code before any actual entry to the browse could take place. The later browse ROW-ENTRY event trigger definition was overriding the earlier one and preventing it from firing at runtime.
FIX:
Consolidate the two browse ?row-entry? event trigger definitions into one. Ensure that there are no duplicate trigger defined for the same event to avoid having the code in the earlier trigger being overridden by the latest definition.