Hi Tommy

This is an issue that has been much on my mind - and on my work agenda - over the last three years, as I'm sure it has for a lot of us.

The short answer is there is no realistic "conversion" from VFP to .NET at the code level and depending on your VFP design, you will want to look at the overall architecture really carefully as well. Somethings that were best practices in Fox are not in .NET. And some VFP apps are not ntier and in .NET you definitely want them to be.

The other thing to consider is data : you don't say what your current data store is so I'll assume it is VFP/DBCs. That's a conversion project in its own right. Don't imagine you are going to write a good .NET app against VFP data.

I think the "conversion" is very much worth doing, but you need to be realistic about what it entails on both the app and data level.

If your prepared to do that, I would suggest you first get a consultant of some kind who understands the issues involved, understands VFP apps, and can get you pointed in the right direction.

(and my personal take is don't hold your breath for a proven "hybrid" solution - i.e. eTechnologia etc. If you want a .NET app, write a .NET app. If you want a VFP app keep what you have and live with it.)

HTH

(and may you continue to goose-egg your tests !! )

>Hi Gang!
>
>Well, I was asked to see what we (as the the Company I work for) need to do to convert over our VFP programs to dotNET.
>
>I was specifically asked to see if there was anything out there that would AUTOMATICALLY convert all or part of the code over to .NET and then we could convert the rest over by hand......
>
>'Thanks for the info....
>
>Tommy