Thanks Hilmar for your prompt reply. As you suggested, I typically use SET STEP ON prior to any debugging as I find that setting a break point is not always reliable.

Which sets up my scenario:

I SET STEP ON and then begin tracing. As long as I step "INTO" performance seems acceptable, but if I step "OVER" a procedure, the debugger "virtually" never returns to the current procedure. It does eventually, but I never have the patience to wait 15 or 20 minutes.

The other two developers on my team are not having these symptoms. I ran a defrag yesterday and will see if I have better results today and will keep you posted.