Is this a bug in access? Stop at code without breakpoint?

[Mark]

Hello all,

I use access 97. Sometimes when I use a breakpoint on a line of code then
press F9 to uncheck it. It will still stop there without a breakpoint when I
run the code. This wouldn't be so bad, but even after I close it and send it
to users it will stop on them at this previous breakpoint.

Has anyone else experienced this and how do I get it to stop?

Thanks!

 

[Marshall Barton]

I use access 97. Sometimes when I use a breakpoint on a line of code then
press F9 to uncheck it. It will still stop there without a breakpoint when I
run the code. This wouldn't be so bad, but even after I close it and send it
to users it will stop on them at this previous breakpoint.

Yes, it is a bug. But, it doesn't seem to happen until your
code becomes a little corrupted. The most common cause of
this kind of corruption seems(?) to be editing the code
while you are in break mode. You may find something useful
at: http://allenbrowne.com/ser-25.html
I urge you to Decompile a COPY of your file. See:
http://www.granite.ab.ca/access/decompile.htm

 

[Tom Wickerath]

Hi Mark,

Yes, this is a known "feature". To prevent code from breaking at a
previously removed breakpoint, do something (anything) to cause your code to
need to be re-compiled. This could be as simple as hitting the space bar to
add a space, then save the module. When you re-compile your code, the
previously saved copy of the P code will be discarded. Manually decompiling
your code, as Marsh suggests, accomplishes the same thing: the previously
saved copy of the P code is discarded. That's the key to eliminating this
problem.

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Hello all,

I use access 97. Sometimes when I use a breakpoint on a line of code then
press F9 to uncheck it. It will still stop there without a breakpoint when I
run the code. This wouldn't be so bad, but even after I close it and send it
to users it will stop on them at this previous breakpoint.

Has anyone else experienced this and how do I get it to stop?

Thanks!