>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.

It is and will be another interesting thread on the topic. I see there are already some valuable information provided in it. As mentioned in this thread, as is the case for pretty much everything in this world, there isn't that much out there about automating everything to do this for your company. But, there are some converstion tools, as listed in this thread, that will help you move towards that goal.

After having done that several times, even when the client requested a conversion as is, it always ended up that adjustment, enhancements or additional components were added into the application, so to benefit from that conversion.

This is always something that has to be considered carefully. There are costs, timeframes, ressources and a lot of additional points that get involved in such a process. There are also a lot of threads in there, blogs and other support forums on the net which contain valuable information on this. But, keep us inform in here so the thread would evolve and we can all provide feedback on your ongoing process.

As for me, even after have done it several times, there is always something new that got brought into it at each occasion. .NET is a great environment, VFP was and still is. But, if your employer wants to convert to .NET, then we will be happy to help as much as we can in this forum.