unwanted Stopmarker in Code (yellow marked line)

[AlexBierig]

Hallo
may be I was looking with wrong keywords - sorry for the German Scool English...
I'm using Access 2019 (part of Office 2019): Retail 7.1.11.27, running on Server 2016


I have an Access Projekt in which the autostart-macro runs a function called Main() as long - this function checks the screen metrics, initalises connections and command-object to an SQL-Server. It also saves the settings from the Access, cuts off the toolbar an so on (this will be restored, when closing Access)

To test some behaviour I set a stopmarker via F9 to check and proof. But I'm afraid, I saved the screen, the code or just closed Access, while the main-function was stooped at the break point, which I set with F9.
This causes now some difficulties:


I can't take off this stop marker (having NO F9 stop-symbol)
I run the function to it's end and saved it, closed the access, edited die makro, compiled it and saved it, saved the form in designer mode, running mode
but this annoying stop resists.
Has someone an idea what else I could do?

regards
Alex

[jojowhite]

Click on that Line of code and press F9 (toggle debugging) then Save (ctrl-S) your code.

[Welshgasman]

And if that does not work, try a decompile and recompile.

[June7]

F9 sets a breakpoint. A breakpoint is identified by a red circle in left margin which doesn't show for you.
In my test, breakpoints are cleared when database closes.
This does appear to be some sort of corruption. If clearing breakpoints from Debug menu doesn't work, nor decompile/compile, create a new module and copy/paste code. Delete old module and rename new. If that still doesn't work, might have to create new db and import from the old.

[isladogs]

This may be due to a 'phantom' breakpoint
Make a minor change to the procedure such as adding a blank line and then save and compile.
This should fix the issue if the other suggestions haven't done so.

[Vstar920AZ♣]

This happens to me on occasion too.
The two things I do that often help are to toggle all breakpoints from the menu bar (that way, theoretically I get them all). Then I move the code down a few lines. Some of these errors seemed to be based on line position and this solves it most of the time.
Sometimes I insert a blank module (this won't help on forms). Then I move the code to the new module.

Viel Gluck!!

[AlexBierig]

Hello together

sorry for the late answer - my wife wanted me doing some holidays at Lake Constance without a computer. So we enjoyed the few days, includung the icy and heavy thunderstorm.
I got a lot of suggests for the solution of my problem.
In my case solved the problem:
This may be due to a 'phantom' breakpoint
Make a minor change to the procedure such as adding a blank line and then save and compile.
This should fix the issue if the other suggestions haven't done so.
AND... an office update, which suddenly raised...

Thank you for helping me

Regards
Alex. Bierig

ps: now I'm looking, if there is a button: solved.

[Welshgasman]

Thread Tools, top right of thread.