>>1. Don't know if I agree with that - mainly because I fall squarely in #2 camp, having used VFP5 debugger maybe 4 or 5 times in over 2 years. WAIT WINDOWs seem to be all I need. The majority of non-trivial bugs I encounter in my apps are MSKB material.
>
>In this case... use the debugger all the time. First, it's much better and easier than WAIT WINDOWs. You'll be convinced of this when you'll really use it!
>
>Second, you'll find much more bugs in your code (before your clients do). Especially the non-trivial ones.
>
>One old and golden programming advice says: "Trace (in the debugger) all your program paths." I know that this is something that almost nobody does, but, from my experience, once you traced at least all the important paths, the code is already much improved. And it's surely less buggy.
>
>Vlad

I'm still working in VFP5. The vast majority of the kinds of bugs I get, the debugger basically blows up spectacularly and I have to kill the debugger/VFP through the NT task manager. An excellent example was my recent thread "SQL: Statement Too Long for no apparent reason". SET STEP ON just before what turned out to be the offending code (MSKB problem, in fact) didn't help at all.

Is the VFP6 debugger substantially improved over that in VFP5?