Are you sure that line of code, the break point is on, is being attempted to
execute? If so, it should break regardless without this particular line of
code being executed. I'm assuming you are working in the MDB file, not a
MDE file, as with MDE, you have no access to the source code itself.
Example:
If X = Y Then
<Do This>
Else
<Do That>
End If
If you have the break point set to the line that has "<Do This>", and "X" is
not equal to "Y", then the code will not stop as that line of code won't get
executed due to the false condition that it will return in that case.
If however, you put the breakpoint on the line "If X = Y Then" and the code
is about to execute this line of code, it should break at this line just
before actually executing the line, thus should give you a change to go into
VBA and debug without this particular line of code being executed.
One other thing that can be done, you could put in the key word, "Stop", as
this will cause the code to break at that particular line, should it be
executed, but I don't like doing it this way cause it's too easy to miss
when cleaning up the code afterwards. It's much easier for the eye to spot
a highlighted break point line then to see a key word, "Stop", cause after
looking over so many hundreds (if not thousands) of lines of code, the code
may not be as much paid attention to.
I not only use VBA's debugging tools, but I have also developed my own
debugging methodology as there are times when using VBA's debugging tools
themselves isn't enough to debug an issue. One such way that I debug, I use
labels on forms, and then have the code report into those labels some
information to help guide me where the issue might be. I usually resort
more so to this sort of debugging in more complex situations.
