James

>
>Actually, the problem with PEM Editor and the debugger really has to do with the trace window in the debugger. PEM editor is just a form with a timer, actually, and the performance for any form degrades if you have the trace window open. That can't be helped (and, believe me, we've spent some time trying).

Maybe you should untick Debug info in Project Options before compiling?

I did and recompiled the app. Before it was slow with all the usual pauses as the code is executed and displayed in the trace window. Now it just flies. Why do you keep debug info on anyway?

Sometimes the simplest things are overlooked.

By the way I do use the PEM3.01, I always have my watch and trace windows open and tabdocked with the properties, command and .View windows and at times the Locals window is also open. My settings are to display the Debug in the Foxpro Frame rather than in its own frame

After removing Debug info and recompiling, I see no slowdown that is greater that say running the class browser or any other app.

Bernard