Stop Statement Doesn't Stop

[Guest]

As a volunteer I create Access databases for non-profits. Frequently, I
encounter code within which the Stop Statement fails and the debugger is not
activated. The Stop Statement is ignored as are breakpoints.

Over the years I have seen several messages posted that address this problem
and several solutions have been offered. None of them seem to work for me.
Among is Microsoft Knowledge Base article 275087. It points out that the
Stop Statement will not work in a *.mde file. I knew that – my problem is
with single user *.mdb database applications.

Also, the “PRB:VBScript ‘ Stop Statement Does not Start Script debuggerâ€
article(252805) that suggests using Regedit to set the JITDebug value to 1,
also doesn’t fix the problem.

Typically, in my case VBA code that has been working, i.e. it compiles,
executes, and both the Stop Statement and the breakpoints work -- suddenly
fails in the sense that while it still compiles and executes, the Stop
Statement and the breakpoints become inoperative.

I do version conversions to accommodate users that have older versions of
Access. That is my only known “sin.†I don’t know if it is relevant to my
problems with the Stop Statement.

 

[Dirk Goldgar]

As a volunteer I create Access databases for non-profits.
Frequently, I encounter code within which the Stop Statement fails
and the debugger is not activated. The Stop Statement is ignored as
are breakpoints.

Over the years I have seen several messages posted that address this
problem and several solutions have been offered. None of them seem
to work for me. Among is Microsoft Knowledge Base article 275087. It
points out that the Stop Statement will not work in a *.mde file. I
knew that - my problem is with single user *.mdb database
applications.

Also, the "PRB:VBScript ' Stop Statement Does not Start Script
debugger" article(252805) that suggests using Regedit to set the
JITDebug value to 1, also doesn't fix the problem.

Typically, in my case VBA code that has been working, i.e. it
compiles, executes, and both the Stop Statement and the breakpoints
work -- suddenly fails in the sense that while it still compiles and
executes, the Stop Statement and the breakpoints become inoperative.

I do version conversions to accommodate users that have older
versions of Access. That is my only known "sin." I don't know if it
is relevant to my problems with the Stop Statement.

One thing that you may not be aware of is that if the option "Use Access
Special Keys" in the Tools -> Startup... dialog is not checked, the
breakpoints and the Stop statement will be ignored.