>>As for why anyone would want to upgrade their app from FP 2.6 to VFP 5.0, I just spent a year and a half doing just that - from the ground up - and am very happy with the results.
>
>Yes, but did you convert all your forms with VFP or design new ones from scratch? If I would think one should have the option in the IDE to set the backwards compatibility off so that you can focus on the methods and properties particular to VFP. In other words, to port all procedural code to VFP buys you nothing, unless you intend to add significant new modules utilizing the OOP aspects of the product...

I think I see where you're coming from...

All my forms came from the ground up - I wouldn't use CONVERT.APP if my life depended on it. As for backward compatibility, I avoid it as much as possible - I'm even moving menus into wrapper classes and I don't use the Report Writer any more.

If you were to read my current code, it would read more like an odd blend of Smalltalk, C++ (without the pointer, of course), and SQL. And as I proceed, more and more of my code is object-based, whether it's stored in a .vcx or in a .prg.