>I haven't seen this particular behavior yet. What I see is that execution is slow when the debugger is open, but never related to its state at compile time. Have you cleared all breakpoints, already?

>I usually test in a second instance of VFP. One I use for writing code and compiling, the other for running the application. Do you still get the same behavior when you do something similar?

To first question: all breakpoints are cleared, no SET STEP ON. To second question: the compiled application will run normally in the second instance of VFP (with the first instance having the debugger open). If I close the second instance of VFP and then try to run in the first instance, the behavior is as described (slow and seems to lock up). What is also interesting is that if I compile and run with the debugger closed, quit, open debugger, then run again, the application runs fast (within bounds of debugger influence). It seems that if VFP has cached the application, then the influence that was occurring is not happening.