"variables that are not dim'd " [are assigned a false  value -
implied/understood]. Got it!


> or currently have a value [ of false?] would cause the
> debug  to start.

Typo?

The implication is that bool Vars are "all" used to
indicate "trouble" when in the FALSE state. Not one of my base
assumptions.


> Use the contents tab of the vba help  to get a programmers reference
> style, for properties, methods, keywords, functions.

Sounds like another good thing to know.


> It good to see you have an interest in debug. It's usually the last
> thing new coders worry about :)

Well... I wouldn't say I'm a new coder, just new to VB. I developed
my own laser light show system in the mid 80's on the, ahemm...,
Radio Shack Color Computer - 6809. Basic OS and assembler display
processor...counting processor cycles and all...real time rotates all
at .98 MHz. ! !
It can be a curse going through all the working code  to remove the
file bloat caused by the debugging  print statements, but my mantra is
that test  and comments (and the algorithim phase - I use flowcharts)
take >> time than writing (actually "entering") the code....