Matthew, I was a bit too enthousiastic ... 8-(
Your proposal works when the VI is started by the ActiveX client, i.e. an event is generated immediately. However, once the VI runs, the value of the control connected to the Value (Signaling) property (set either manually or via the Active X client) is only transfered from the control into the property (and generates an event), if the control and property are placed in a while loop. This loop contains a wait object, such that the VI does not consume all CPU time. At that moment, the approach tends to be more polling-based than event-driven. Also, the response time depends on the wait value set in the while loop (and the time it takes to perform the actions within the while loop). Another disadvantage is that this approach will generate an event during each iteration of the while loop (generates an event even if the value remains unchanged). Please let me know if I'm overlooking something. Could you also verify what's wrong with the link you provided ? Regards. Frans.
