A97: Module window, clicking in vertical bar on left side of window...

[MLH]

In Access 97's module window, clicking in vertical bar on left side of
window causes individual lines of code to be hilited - nothing like
this at all ever happened with Access 2.0. What is this all about?
What use can be made of it?

[Wolf]

It's a breakpoint, used to pause code execution at the highlighted line
for debugging purposes. Personally I prefer to use the keyword 'stop' .

[MLH]

No wonder my code was not running correctly! I thought the hilites
went away if you closed the module window. Not true! They're
remembered & acted on as you have said here. Thx for update!
I too prefer the STOP keyword.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

It's a breakpoint, used to pause code execution at the highlighted line
for debugging purposes. Personally I prefer to use the keyword 'stop' .

[Trevor Best]

MLH wrote:

No wonder my code was not running correctly! I thought the hilites
went away if you closed the module window. Not true! They're
remembered & acted on as you have said here. Thx for update!
I too prefer the STOP keyword.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

It's a breakpoint, used to pause code execution at the highlighted line
for debugging purposes. Personally I prefer to use the keyword 'stop' .

The breakpoints aren't guaranteed to be remembered so if you want to
close and reopen the app and debug, assume they won't be and use the
stop keyword. If you want to close and reopen and not debug, assume they
will be remembered and clear them all.

Rather than having to clear up a load of stops for runtime you can use a
conditional stop using either a variable or a constant, e.g.

Global gfDebug as boolen
if gfDebug then
stop
end if

or using conditional compilation...

#const gcfDebug = True
#if gcfDebug then
stop
#end if

or even make use of Debug.Assert

--
[OO=00=OO]

[MLH]

Nice! Many thx.