Unless the wizards have changed since VFP 5, the code transferred from FPW screens gets moved to methods in VFP forms that I really would not have selected. For example, I made heavy use of Valids in FPW screens which gets directly moved to the Valid method of the VFP from by the conversion wizard. I can't think of 5 instances where I use the Valid in a form anymore. My data validation is usually taken care of in the LostFocus of the control, specific subclass of the control, a form method that validates all the data at once, update triggers or anything else other than the Valid method. I just do not handle data validation in individual controls anymore.

It is not that it won't work, it is just that when I did this, I spent an inordinate amount time moving code where I wanted it, changing obsolete code to take advantage of VFP enhancements, getting the controls on the form positioned, etc.

Compared with the time it took to convert the forms completely, I could have just redone the forms from scratch myself especially if you have created a good set of subclasses of all the VFP base classes.

In your case, use the conversion wizard to convert some screens to forms and try them out. Then do an evaluation on what the best approach for you will be.

I also found that most of my procedural code could either be moved to PRG-based classes or done away with completely.

>Mark,
>Thanks for your advice.
>
>I have converted a few small forms to see what would happen and it gave me some hope. The project I need to upgrade is fairly large and , with the time constraints, wont be practical to re wite from scratch.
>
>Do you have any particular reason for advising against an update ?
>
>Regards,
>
>Gerard