Has anyone had the problem of code executing past break points?

[spurs]

I have been having sporatic issues lately (last month or so) while trying to debug code by using a break point, the code executes past the break point.

I have found on occation that removing the password protection on the macros fixes this temporarily but then it returns
I have at times had to close the workbook and reopen and it works for a bit then stops working again

Microsoft has not been able to help with this - any suggestions on where to look to fix this?

 

[Micron]

Can't recall for sure but I think I've had this happen because that's how I learned of the Stop command. Put that where you want the code to pause but don't forget to comment it out when done.

 

[spurs]

Thank you for this
stop does work ;
unfortunately it is an extra step

the inconsistency of brak point is very annoying. After over 25 years of using break point i have never seen this happen before a month ago

 

[Micron]

Are you in the habit of compiling your code? It is possible that the text you see on a code page does not match what has been compiled. Just saving is not enough. If compiling doesn't solve the issue, I suggest you copy all, paste in a notepad file, remove code, save, compile, close and save wb, re-open, paste from notepad, save and compile. I recommend you back up the wb first.

 

[spurs]

Micron
I have never intentionally compiled my work, but its possible that I may have clicked on debug and the compile key was accidentally pressed.

How can I verify if I have?

 

[Micron]

If the code is compiled, the compile button on the toolbar is greyed out.

 

[spurs]

Thanks
No my code was not compiled