■ During debugging, you used the Set Next Statement command
  to specify a statement that is in a procedure other than
  the one where program execution is suspended. Visual Basic
  ignores the Set Next Statement command.
 
■ Possible solution:
 
  • Move the suspended procedure into the code window and, if
    you still want to use a Set Next Statement command, use
    it to start running from a statement in that procedure.
 
■ If you need additional help, move the cursor to a keyword
  and press F1 to open the Help window.