value-changed trigger on dynamic browser

[jeffcoop_69]

I'm having problems with my value-changed trigger firing on a dynamic browser I'm creating. Is this a known issue or am I doing something wrong? Progress Version 9.1c - sample below: (also tried it with the triggers statement as part of the assign and other triggers appear to work)

CREATE BROWSE BrowseHdl
ASSIGN
FRAME = FRAME {&Frame-Name}:HANDLE
X = 5
Y = 120
WIDTH = 75
DOWN = 5
QUERY = QueryHdl
TITLE = "Browse"
VISIBLE = TRUE
READ-ONLY = FALSE
SENSITIVE = TRUE
SEPARATORS = TRUE.

ON value-changed OF BrowseHdl DO:
MESSAGE "trigger"
VIEW-AS ALERT-BOX INFO BUTTONS OK.
END.

 

[Norman Biggar]

CREATE BROWSE BrowseHdl
ASSIGN
FRAME = FRAME {&Frame-Name}:HANDLE
X = 5
Y = 120
WIDTH = 75
DOWN = 5
QUERY = QueryHdl
TITLE = "Browse"
VISIBLE = TRUE
READ-ONLY = FALSE
SENSITIVE = TRUE
SEPARATORS = TRUE
TRIGGERS:
ON value-changed
PERSISTENT RUN p-ValueChanged IN THIS-PROCEDURE.
END TRIGGERS.

PROCEDURE p-Value_Changed:
MESSAGE "trigger"
VIEW-AS ALERT-BOX INFO BUTTONS OK.
END PROCEDURE.

 

[jeffcoop_69]

Thanks that worked.

During my investigation I came across Knowledge Base #22047:

This Solution describes the functionality of the undocumented client
startup parameter, -extravc.

In Versions 8.x and 9.0B, when clicking on the current row of a
browse, the VALUE-CHANGED trigger is fired. In version 9.1A and
higher, this trigger is only fired if the value has actually changed.

SOLUTION:

Beginning with the patch Version 9.1B01, a new client startup
parameter (-extravc) has been added in order to ensure the Version 8.x
behavior can still be used.