If you want VFP to continue, create and put in place as many VFP apps as you can. Do your very best to show the world how great VFP is by sticking it in their face. In every 'about' form I say something like 'Created with Visual FoxPro Version 9 SP1'

Grady,

This assumes that you have the decision on the development tool. If the decision isn't yours, if it belongs to a client or a development shop, odds are high that it won't be VFP. Odds are at least higher than miniscule that the shop/client is transitioning from VFP to .NET or something else.

If the decision is yours, then you're doing so with the knowledge that someone other than you may ultimately need to maintain that app. And the # of qualified and available VFP people is shrinking.

Bottom line....and I mean this literally....and I'll take on all the flaming....anyone doing "File....New Project" in VFP for client work is quite likely doing a disservice to his/her client. I don't mean that in a mean or snide way, it's just the truth.

Thirdly, brag about it to every developer and geek you speak with. There are so many good things about VFP that, with a little practise you'll be able to diplomatically crush any argument they come up with.

Sure, VFP has a large # of good things. But the ultimate trump to that argument - .NET will continue to grow, and VFP won't.

Look, if you want to continue trying to use VFP to do so, go right ahead. But if any of your clients someday ask you why you knowingly used a product that Microsoft stopped building, I hope your answer is better than your "I'll show you, Microsoft!" motive.

Grady, I've read some of your messages before. I may not agree with everything you say, but you seem like a pretty sharp guy. Too sharp to let your emotions on the subject get the best of you.