Phantom Breakpoints--what causes that?

[jsteph]

Hello,
In Access 2003, sometimes when I run a process the code stops with the yellow highlight on a line--with no breakpoint. As I look at the line, I recognize it as one that I may have been testing a week ago or so, but I'd since removed the breakpoint, and completely closed the application. Yet it decides to stop there still. This isn't easily reproducible, it just happens sometimes. Is anyone familiar with this and do you know why it happens and how to prevent it?
Thanks,

 

[Ed2020]

jsteph,

Yep, you've found another one I've seen as well. I used to get this in A2K occasionally as well. As all my users are accessing the systems in runtime Access it isn't a particular problem.

I've put it down to yet another A2K3 "feature".

Ed Metcalfe.

Please do not feed the trolls.....

 

[jsteph]

Thanks Ed...I was afraid of that,
--Jim

 

[CautionMP]

jsteph,
I ran into this a long time ago, as a result I started using [tt]Stop[/tt] statements in my code instead of break points.

As a final thought, here is a best practice from one of the forms, put the [tt]Stop[/tt] in an if statment so you can toggle it off and on without having to remove them manually from your code.

Option Explicit
[b]Public blnTesting As Boolean = True[/b] 'or False
...
Public Sub One()
...
If blnTesting Then Stop
...
End Sub
...

Hope this helps,
CMP

[small]For the best results do what I'm thinking, not what I'm saying.[/small]
(GMT-07:00) Mountain Time (US & Canada)

 

[RuralGuy]

I believe a /decompile will rid the file of those phantom breakpoints.

http://www.granite.ab.ca/access/decompile.htm

HTH RuralGuy (RG for short) acXP winXP Pro
Please respond to this forum so all may benefit