"davidm" wrote in message

Thanks, Peter, for your input. The global variable (bExit in the
example) can ensure the event fires but once only if it (the global
variable) is used elsewhere in other procedures in the module. Do you
suggest, I introduce the variable in all these other procedures (15 of
them) and set bExit =false next to Exit Sub?

Possibly, depending on what you are doing, Eg -
Say you have code to loop through sheets resetting the up/down state (value)
of activeX togglebuttons as relate to each sheet. You don't want the code in
the click event to do anything if the value changes.

In each click event
If bExit Then Exit Sub

In the main routine, as per original example, bExit = True before the loop
and false at the end.
You could also set bExit = True in all routines that might trigger events
you don't want processed, eg
If bExit Then Exit Sub
bExit = True
'code
bExit = False

Be careful to ensure bExit is reset False when done, normally best to
include an error handler as in original example.

Maybe, guessing, you only want click event processed depending on the state
of the new value, eg

If myToggle.value = true Then
'do normal code even if bExit = True
Elseif bExit Then
' do nothing
Else
' some reset code
End if

Regards,
Peter T