>
>For now yes. But if I start using C# or VB.Net and reach some level of profeciency, do you think there are still compelling reasons of using VFP side by side? IMO and the way I see it, all I can do with VFP can be done with .NET tools. On the otherside, there are things that I can do with .NET tools but I can't in VFP without third party help. Before, the VB vs VFP is so interesting topic to throw argument with, but today, it's C#.Net vs VB.Net. Sure I can use existing MTDLLS but will gradually be converted into the tool of my choice.
>

Jess;

Just my take. We use third party tools with VFP to increase our productivity. Such tools may include but are not limited to frameworks and tools like West Wind Connection. It takes less time to use such tools to create traditional desktop or web applications. If it is important to save time and money then VFP and third party products are worth considering.

I am sure that .NET is only another tool and will have its proper place. By using available tools correctly you can employ them to assist you to create professional products. Use the proper tool for a job – not the latest or oldest technology. Your job is to determine what is the best tool. There is no one tool that will “do it all”!

Tom