>Conversion is, for all intents and purposes, not a good idea. Think about moving from Fox 2.x to VFP. The languages were the same, but applications are done differently in VFP. The converter created Formsets, which are considered a bad thing to have.
>
>.NET apps are typically architected differently that VFP apps. The languages are different. My advice is to prioritize different modules of your app. Take the first one and spec it out. Document the functionality. Then start rewriting it in .NET. You'll learn ALOT and the second module will be very different. Don't be afraid to go back and refactor the first one.
>
>>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

Thanks for the help !!