techexpressinc
Registered User.
- Local time
- Yesterday, 19:30
- Joined
- Nov 26, 2008
- Messages
- 185
removing a break point
- Thread starter techexpressinc
- Start date
These two statements are contradictory
Could you elaborate.
SpentGeezer
Pure Noobism
- Local time
- Today, 09:30
- Joined
- Sep 16, 2010
- Messages
- 258
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
Pure Noobism
- Local time
- Today, 09:30
- Joined
- Sep 16, 2010
- Messages
- 258
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
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
Last edited:
techexpressinc
Registered User.
- Local time
- Yesterday, 19:30
- Joined
- Nov 26, 2008
- Messages
- 185
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
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
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
Registered User.
- Local time
- Yesterday, 19:30
- Joined
- Nov 26, 2008
- Messages
- 185
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
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
Smeghead
- Local time
- Yesterday, 16:30
- Joined
- Jan 12, 2001
- Messages
- 32,059
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.
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
AWF VIP
- Local time
- Today, 01:30
- Joined
- Jun 26, 2007
- Messages
- 2,642
Re: removing a break point - solved in Jan 2011
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.
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
New member
- Local time
- Today, 00:30
- Joined
- Sep 19, 2011
- Messages
- 2
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.
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
Smeghead
- Local time
- Yesterday, 16:30
- Joined
- Jan 12, 2001
- Messages
- 32,059
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.
Similar threads
