>Actually, I'm not anti-.NET. On one project I was working with I decided to go with VB.Net and it was driving me nuts, but little by little I started to get the hang of it and it had some really nice features, like a lot of people were saying here, don't knock it until you try it and I definitely wanted to explore it more, unfortunately b/c of time constraints I had to use VFP to finish the project, so for certain projects I think .NET is an excellent tool. The problem now is that if I have a new project where VFP is a perfect fit I don't think it would be wise to use it since I don't know what type of support or new anti-foxpro announcement microsoft is gonna come up with since it's a "business" and money is the bottom line, and I'm working in my clients best interests so I might be forced to use a tool that is not the best for the job, if I use foxpro what if they have a service pack for Vista and it messes up foxpro?, what am I going to tell my client? Basically now I need to use
>another tool for a project like that and either eat the cost or charge my client more.
>
>But we are programmers and tools will come and go with time and we need to adjust to the market, like you mention have a positive attitude and honestly I do, but that doesn't stop me from lamenting the faith of a tool that is a GREAT tool for thousand of developers and customers around the world, I think the bottom line is that customers are losing, especially the thousands of small shops that don't have a big budget but foxpro is doing wonders for them, so if I'm doing anything it's defending customers.

Ditto.
Fox was the greatest tool for developers and customers but its 'isolated' nature didn't leave much room for MS in terms of income.