The part of that statement that attracted my attention was "Fox positions pay higher than their counter parts in VB". But if you figure that money isn't everything, I won't argue.

>Hi David ---
>
>There are some of us, albeit slowly due to commitments, who are working hard at providing code blocks and case study rewrites based on VFP. I agree with John on the point of...what is the problem? The reply you got speaketh the truth and you have to remember that VB is a strategic interest to MS while VFP is not so much so. If VFP died tomorrow, MS is not hurt, but if VB died, they'd be in a world of hurting.
>
>Remember, we are outnumbered about 10:1. This makes it even MORE important that we have a tight-knit community, that we send successful apps to VFUG and MSDN to use as case studies, et al.
>
>
>>I recently took advantage of Microsoft Support and used it as a forum to express some personal feelings I have about FoxPro. I'm on the verge to move into Visaul Basic for various reasons in spite of how much I like working with FoxPro.
>>
>>Here's the response I received.
>>*******************************
>>
>>I understand your frustration about the lack of examples of code in FoxPro. The support groups seem to be getting a little better for FoxPro, but unfortunately are far from level of other languages such as Visual Basic. Probably the best sources of information are the Knowledge Base on Microsoft's website, the Universal Thread, and any local Users Groups you might have in your area. The upside of this dilema is that due to fewer FoxPro Developers on the average Fox positions pay higher than their counter parts in VB. And now that we have increased our FoxPro staff hopefully we can help you with quicker responses.
>>
>>Brian Shreves
>>FoxPro Developer Support
>>
>>For comments, questions or feedback about the customer service you have received please email
>>Tell_Us@Microsoft.com