>I am migrating my 2.6 application to VFP 5.0 and am finding that I have to not only re-write the whole thing, but that debugging doesn't work the same way as it did in 16bit. For instance, the breakpoints don't work consistently, and so in order to watch values change, I placed a
>ACTIVATE WINDOW TRACE
>SUSPEND
>in the Init method of a form, which generated a GPF. I have had GPFs in other instances, where, I suspect, a bug occured in my application.
>Also, when I test things in the command window, I often get the error message "Variable UTemp not found". This is not very helpful. My question is: is my version of VFP 5.0 buggy and if so, are there patches available? Thanks very much...

Hi Robin,

Service Pack 3, which is available from the MS download site will upgrade VFP 5.0 to 5.0a, and, yes it does fix some bugs. Personally, I've found the debugger in 5.0 to be far superior and more reliable to that in FPW 2.6. BTW, trying changing that line from ACTIVATE WINDOW TRACE to ACTIVATE WINDOW DEBUG and see if the GPF problem goes away. The latter works fine in 6.0.

hth,