From the "Thanks...but" Department...
> ...snip...
> Use the contents tab of the vba help  to get a programmers reference
> style, for properties, methods, keywords, functions.

I went back and looked, but it's the same info I saw by doing my
search for the debug  info. Sorry, but perhaps you didn't catch my
remark:
> > Help seems pretty malodorous as well. ...
a.k.a. stinks as usual.

For Debug.Assert BoolVar, the Help says:
> > "Conditionally suspends execution  ...

> > Conditionally ? What condition? What is the BoolVar for?

Then I speculated:
> > Shouldn't Help say: "When BoolVar (or argument)
> > is FALSE, suspends execution ...

Since I'm not formally schooled in the ways of the Borg (said semi-
affectionately), I wouldn't know that things  happen on a FALSE
condition when they are done "conditinally". At least that is the
implication. I am used to naming things by what happens when the
variable / signal is high or asserted.

Halt -> when high or asserted then STOP
Run -> when high or asserted then GO
Run = *Halt , or HALT bar, or NOT HALT if you prefer. SO I
expected the Debug thingy to be "asserted" (halt execution) when
sumptin' is TRUE.