set next statement
Thanks
Dick
Thanks
Dick
Hmmm... using Ctrl+F9 works for me (if I'm using the Visual Basic Express profile) I have seen some issues where the profile wasn't loaded correctly, in which case the default keyboard settings may be somewhat different (i.e. Ctrl+Shift+F10)
If you press F2 in a code editor window, does the object browser show? (Just trying to narrow down why the Debug.SetNextStatement keyboard binding isn't correct on your machine)
Best regards,
Johan Stenberg