Code Changes Not Taking Effect / Breakpoints Not Hit

[vthokienj]

I have been noticing over the past several days that changes in my code are not taking effect when implemented. When I try to put breakpoints in to find out why, those breakpoints are not being hit either.

There is no chance that I am mistaken and something else in the program is causing this behavior. This occurs in many places. For example, I have a simple for loop 1 to 10 that outputs 10 columns of data. If I change the 10 to a 5, only 5 columns would draw. But when I change back to the 10, 5 columns still draw.

I can sometimes close Excel and reopen, and the same thing is occuring. It seems almost random when it will decide to go back to using the 10. And putting the breakpoint to see the count variable will not be hit, yet the code is clearly executing as the output displays.

Is there something that could explain this behavior? I have been working with this program for many months so I am quite familiar with it which is why I am sure it is not something in another part of the code causing this.

Thanks for any help.

 

[Jerry Sullivan]

That does sound strange.

If the code isn't hitting the breakpoints that you expect it to hit, perhaps stepping through the code using F8 will show you where it's going instead.

You've probably already considered these, but here's some possibilities that come to mind....
1. An error handler is causing your code to skip unexpectedly but it appears to process normally.

2. Similarly named functions in the same project- maybe one with Private Keyword and one with Public.