>>I know I have seen some threads where some problems were reported in upgrading VFP 3.0 apps to VFP 5.0. Specifically, is there a compiled list of these problems yet. I tried to search the historical threads without success. My client wants to know what to expect if he requests us to upgrade from 3.0 to 5.0. Please point me in the correct direction. tia Steve
>
>Hi Steve,
>
>I don't have complete list of problems, but when I converted my project, I had to change the code in all places where it called SetFocus() from Valid(), in many cases I just moved it to LostFocus(). Then there were visual changes in forms because of default font and alignment changes. Well, that's almost all I remember :). I know Michel had something else.
>
In addition, I recall a few other problems: in vfp5 afields() includes Name, so you must use Name clause with this in Create Table in vfp5 to avoid DBF naming problems...some reports converted had a couple of odd little problems, and I had a DBC corrupted on conversion.

But the benefits far outweigh any problems, of course...the load time of my largest app was cut in half with vfp5...