mateomateo
asked on
Unable to remove breakpoints - phantom breakpoints
I have noticed that sometimes visual basic code I am running will break on a certain line, even after I have removed the breakpoint.
I am running my Visual Basic code in Microsoft Access.
What causes these "phantom" breakpoints to remain in the code, even after I have cleared and removed all of them.
This happens very infrequently but is very frustrating!
Any ideas?
Thanks
I am running my Visual Basic code in Microsoft Access.
What causes these "phantom" breakpoints to remain in the code, even after I have cleared and removed all of them.
This happens very infrequently but is very frustrating!
Any ideas?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Generally, rebooting will clear the phantom breakpoints ...
mx
mx
ASKER
I can't remember if I used that keyboard shortcut, but i definitely went to that option in the menu to remove all breakpoints.
The only way that I had found to fix it was to delete the code for the whole procedure, save the Access file, then reopen the Access file, and then re-paste the code in where it was before.
I rarely use watches, and there were definitely cases where it was happening and I had never used a watch in that area of the code.
Based on how that was the only way I could fix it in the past, does that make you think of any other possible causes?
I think sometimes if stop the code in the middle of debugging, before removing the breakpoint. That seems to cause it to happen i think.
The only way that I had found to fix it was to delete the code for the whole procedure, save the Access file, then reopen the Access file, and then re-paste the code in where it was before.
I rarely use watches, and there were definitely cases where it was happening and I had never used a watch in that area of the code.
Based on how that was the only way I could fix it in the past, does that make you think of any other possible causes?
I think sometimes if stop the code in the middle of debugging, before removing the breakpoint. That seems to cause it to happen i think.
Also, if you have a BP set, and you Save the code then close the db ...
mx
mx
Is the code simply "Breaking", or is it actually breaking at a "Point" you never set?
In other words, is the "BreakPoint" designation present when the code breaks?
...if I am understanding your question...?
untitled.JPG
In other words, is the "BreakPoint" designation present when the code breaks?
...if I am understanding your question...?
untitled.JPG
ASKER
boaq2000:
It looks like your screenshot BUT WITHOUT the brown dot there.
There WAS a breakpoint there before, but it had been removed, before the code was run again(normal not debugging mode)
So I removed the breakpoint, but it still broke the code at the breakpoint, even after it was removed.
It looks like your screenshot BUT WITHOUT the brown dot there.
There WAS a breakpoint there before, but it had been removed, before the code was run again(normal not debugging mode)
So I removed the breakpoint, but it still broke the code at the breakpoint, even after it was removed.
Yes ... I get it ... I have seen many over the years. Again, reboot has always cleared them out. Various odd, hard to repeat reasons for occurrence ...
mx
mx
ASKER
Ok, I am about to split up the points for this answer.
Does anyone have any other suggestions besides reboot?
Or my solution of copy the code to text file, delete code in module, save module, close database, re-open, paste code back again.?
Does anyone have any other suggestions besides reboot?
Or my solution of copy the code to text file, delete code in module, save module, close database, re-open, paste code back again.?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've noticed that the phantom break point think seems to be synonymous with increased sun spot activity ... just an fyi ...
mx
mx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"Does anyone have any other suggestions besides reboot?"
This only happens to me on a very infrequent basis ... like, I don't think it's happened to me so far this year. I think the bottom line is ... BP's just get 'stuck' sometimes ... a fact of Access Life.
May The Code Be With You ....
mx
This only happens to me on a very infrequent basis ... like, I don't think it's happened to me so far this year. I think the bottom line is ... BP's just get 'stuck' sometimes ... a fact of Access Life.
May The Code Be With You ....
mx
ctrl + shift + f9
to clear all breakpoints