My understanding is that when I get an out-of-range subscript it is supposed to put me in the routine
where that occurred so I can look at variables in the same routine.
What is actually does: is put the little blue arrow in a place that has NOTHING to do with the routine,
so I cannot look at any variable in the routine. The call stack is completely wrong as well, so I cant use that either.
so - - I have to go back and insert a breakpoint(F9) near where the problem occurred, and/or stick in print statements, etc.
and run it again.
The text in the output is correct, BTW, it does tell you what line number, etc.
Ths problem seems to come up when the breakpoint is within an internal routine, i.e. one that comes after a CONTAINS statement.
Its a minor annoyance, but still I cant help but wonder why they did not test this ?? VS has been around for a long time, right ?