The problem for me with Stop is that you have to amend the code to add it,
and then remove it again later. If you break at many different points in a
large program, this becomes a headache.

I would also suggest that Stop is a legacy of previous versions of Basic,
before we had any decent debugging tools. Breakpoints, stepping code, Watch
items, etc., are more sophisticated and more flexible.

--

HTH

RP

"JMCS" wrote in message
...
Thanks, Bob

You didn't answer my question, but your suggestion helped me solve the
programme problem.

I'd still like to know what is going wrong with "Stop" as I've being using
it without problem for over 12 months (limit of my exposure to Excel VB)

"Bob Phillips" wrote:

Use breakpoints, that is the norm.

--

HTH

RP

"JMCS" wrote in message
...
My programme is not doing what it's supposed to.

My standard approach (used successfully many many times and presumably
the
morm)) in such cases is to put "Stop" in just before the relevant code
line,
and then step through the code line-by-line. However, if I do this in
this
particular case, the programme carries on through as normal, doing all
the
instructions around the Stop, and completely ignoring it.
Suggestions,
please?