>Does this mean that you would not recommend using any of the conversion approaches or is any one better than the others?
>1) minimalist approach - running 2.6 code and screens in the 6.0 environment
>2) incremental functional approach - convert the code and not the screens
>3) incremental visual approach - run the conversion over both the code and the screens and then have to copy the code from the screens into the forms
>
>A complete rewrite of the software is not an option for us.
>
>These approaches were obtained from appdev.com, vfp free courseware.

If you are only going to convert for the sake of converting, why do it? You will gain nothing, and the maintenance of the application will be horrible. If you really look at the time necessary for a rewrite and compare to the continued maintenance of a converted application, you will probably find that the time to do each is about the same.

VFP is a rich language with all kinds of features that you will not benefit from if you simply run your current code in it. Ie, there's no reason to convert.