>>>When you get into this situation, which also happens to me too frequently and causes me to just use SET STEP ON more than I'd like, the run to cursor feature usually does not work, either.
>>
>>The only time when I noticed it doesn't work is when it encounters another breakpoint before reaching the cursor line.
>>
>>As a sidenote, I've found that the NextStatement actually enables you to skip lines of code. Helps a lot when getting to your point of interest takes a long time, and there's a line you know will break it - just put your cursor on the line after that, and in the menu click 'Next statement' (or next command, whatever), and the debugger will skip all the lines between the current and that line. They won't be executed.
>
>I use Set Next Statement a lot. Mainly to skip code that I don't won't executing because a previous problem will cause it to fail, yet I want to get out of the code gracefully. I don't use it much the way you mention. It would seem that using it that way would often result in errors in the later code because it would often depend on the preceeding lines executing.

Most of the time, the offending line is an assignment - do that in the command window, skip the line and you even have a line left in the command window that you can drag and drop into your code later. Some other times it's a call which you know will fail, but then doesn't really mean much at the moment, you just want to get your code to go to a certain point that interests you, so you skip that and get where you want.

So our usages of the Next Statement aren't different. We just described it differently.