Phantom debug break points in MS Access VBA code.

  • Thread starter Thread starter Chrisso
  • Start date Start date
C

Chrisso

Hi All

I debugged a problem on a colleagues PC and used a break point on a
line of VBA code. I fixed the problem, removed the break point and
walked away happily.

Since then this colleague keeps reporting that VBA *stops* at this
"phantom" break point each time the code runs! The VBA editor comes up
with the line highlighted where I *had* the break point but it is no
longer marked - but the code still stops.

As you can imagine this is causing acute confusion and embarassment
for me.

Does anyone have experience of such a problem? How do I make sure that
the break points are cleared completely? I am desperate! :)

Thanks for any ideas,
Chrisso
 
Hi All

I debugged a problem on a colleagues PC and used a break point on a
line of VBA code. I fixed the problem, removed the break point and
walked away happily.

Since then this colleague keeps reporting that VBA *stops* at this
"phantom" break point each time the code runs! The VBA editor comes up
with the line highlighted where I *had* the break point but it is no
longer marked - but the code still stops.

As you can imagine this is causing acute confusion and embarassment
for me.

Does anyone have experience of such a problem? How do I make sure that
the break points are cleared completely? I am desperate! :)

Thanks for any ideas,
Chrisso
Click to expand...

Hey Chrisso,

I had the same problem and had to decompile the application. I can't
swear this will help you but it sounds like you have the exact same
problem as me. There are several postings already on how to decompile
an application just remember to save the original application
somewhere before doing the decompile.

Ray
 
Select the breakpoint line...Cut it.

Move the cursor down, or up, a line..and paste.

HTH - Bob
 
Select the breakpoint line...Cut it.

Move the cursor down, or up, a line..and paste.

HTH - Bob
Click to expand...

Thanks very much Ray & Bob. I tried Bob's suggestion as it seemed
quicker and it worked a treat.

Thanks
Chrisso
 
Chrisso said:
I debugged a problem on a colleagues PC and used a break point on a
line of VBA code. I fixed the problem, removed the break point and
walked away happily.

Since then this colleague keeps reporting that VBA *stops* at this
"phantom" break point each time the code runs! The VBA editor comes up
with the line highlighted where I *had* the break point but it is no
longer marked - but the code still stops.
Click to expand...

FWIW that's why I started inserting Stop statements.

Tony
 
Back
Top