|Subject:||VBScript, event sinks and repeated error messages inside the call-back functions|
|Posted by:||R.Wieser (addre…@not.available)|
|Date:||Thu, 23 May 2019|
I've written a simple OCX which sources some timed events and cause callback
code in my VBScript to be executed (initiated by way of the second argument
in a CreateObject( ) call).
The problem is that when I make a mistake in the scripts callback code I get
a continuous stream of error dialogs (one for each event).
- Is there a mechanism with which I can have my OCX check if the scripts
engine is in an error state (so it can suspend its sending of the timed
- Should I be using another approach, and if so which one ?