I thought of using an "ignore bit", but had to ask the other question first.

Yes. When writing and debugging the code, an error occurring when events  are
disabled
requires manually re-enabling them before anything works again.

While fitting this into my brain, I see that the same technique will work
for inhibiting the
Sheet_Change event  when changing cell values. The routine needing to change  a
cell value
simply sets NestedCall (to true) and changes away... Another variable, but hey,
they're
pretty cheap. (:-)
I can, instead, call my variable EventsOff.... Or EventsOn and get rid of
all the "Nots" and
the somewhat awkward "If negative Then" . Looks like only one var is needed for
the
whole Project.
Cool.