removing a break point

[techexpressinc]

I had some break points - I cleared them. But everytime I start the DB the code displays and stops in debug mode.



I cannot get the code debug screen from appearing. Any ideas?

Attached is what happens.

Thx
Russ

 

[Rick_A]

My first thought was to make sure that a control named "CoName" exists on the form--make sure it's not misspelled or something.

 

[vbaInet]

These two statements are contradictory

But everytime I start the DB the code displays and stops in debug mode.

I cannot get the code debug screen from appearing.

I cannot get the code debug screen from appearing.

Could you elaborate.

 

[SpentGeezer]

These two statements are contradictory


Could you elaborate.

Fair go....,it is just a typo:

I cannot get the code debug screen from appearing.

should be

I cannot stop the code debug screen from appearing!

 

[SpentGeezer]

I had a similar problem once, and fixed it using the following methodology:

Remove the offending If is Null(coname....) end if staement completely.
Save.
Close and reopen.
It should work now (without that test obviously).
Now put the statement back in and save and close etc...

TECHNICALLY THIS SHOULD NOT SOLVE ANYTHING, BUT FOR ME IT DID. WOOOOO

 

[vbaInet]

One can only speculate Spent.

If that was just misinformation then we need to know what the error message is.

 

[techexpressinc]

Re: removing a break point - SOLVED - werid solution

SpeedGeezer - I did what you said and it worked!

"using the following methodology:

Remove the offending If is Null(coname....) end if staement completely.
Save.
Close and reopen.
It should work now (without that test obviously).
Now put the statement back in and save and close etc...

TECHNICALLY THIS SHOULD NOT SOLVE ANYTHING, BUT FOR ME IT DID. WOOOOO"

Thx Russ

 

[ewc]

I've seen these undocumented break points in code since Access 2003 and continue through Access 2010. The only success I have had is to stop on the code line producing the stop and remove breakpoints (Debug menu, Clear all breakpoints) but then force an empty line in place of that location by hitting the enter key. Save the change and then Compact and Repair Database and somehow, the problem disapears. You can then go back and remove the blank line. Seems like an Access bug.

 

[techexpressinc]

Re: removing a break point - solved in Jan 2011

I am not sure how to mark items solved in this forum.

The solution was = delete the code and re-install the code.

Russ

 

[boblarson]

Re: removing a break point - solved in Jan 2011

I am not sure how to mark items solved in this forum.

The solution was = delete the code and re-install the code.

Russ

We don't have a way to mark solved.

Oh, and as an addendum to this thread -

One way to avoid the phantom breakpoints (as well as other code problems) is to NEVER edit code while in break mode. Always stop the code and put the form or report into design view. What happens if you don't is that sometimes the VBA compiler and the compiled code get out of synch and can cause problems including the phantom breakpoints and corruption.

 

[Guus2005]

Re: removing a break point - solved in Jan 2011

We don't have a way to mark solved.

Oh, and as an addendum to this thread -

One way to avoid the phantom breakpoints (as well as other code problems) is to NEVER edit code while in break mode. Always stop the code and put the form or report into design view. What happens if you don't is that sometimes the VBA compiler and the compiled code get out of synch and can cause problems including the phantom breakpoints and corruption.

I never knew that! So the problem should also go away when you decompile and compile the code again? I must try that sometime.

Selecting the line and ^x^v^s will be history then.

 

[FrankBrierley]

Hi Just Joined the forum and noticed your query, dont know if you have found a solution yet but this worked for me.

Edit the offending line of code, save your object and run the code with the line edited out.

Unedit the the line and that should have fixed it.

 

[boblarson]

Hi Just Joined the forum and noticed your query, dont know if you have found a solution yet but this worked for me.

Edit the offending line of code, save your object and run the code with the line edited out.

Unedit the the line and that should have fixed it.

Not only is it kind of strange to be posting a solution to a thread that was already solved, but that it was a long time ago, but the best solution is the decompile and then recompile, regardless of this suggestion working or not. The decompile fixes the VBA synch discrepancy which is what this is caused by and it will also take care of other issues that might not be known at the time.