VB is MS's cash cow. At least it is the "preferred" language for writing to one of the real cash cows - SQL Server. Why should MS push VFP, which is faster, better, bigger, stronger, etc. in many instances, when they can sell something that cost per connection?
I am in the process of learning VB, only because it can do some things that VFP can't and there's such a huge market for VB. However, given the opportunity to develop an application, I will most likely write the front ends and middle tier in VFP. If I can save a client money and deliver as good or better performance, it only makes sense to use VFP over VB. Many businesses have no need for SQL Server and VFP will cost them much less and many times perform better.
I would hate to give up the ability to create my apps in VFP and be forced into the VB way of doing things - "SLOWLY!"
John Harvey
Shelbynet.com
"I'm addicted to placebos. I could quit, but it wouldn't matter." Stephen Wright