Hi John (we gonna sing friday again :) )

>I think there are several reasons. I could be wrong on some or all of these, but here goes:

I think your reasons are very insightful, and I think you are right as to why.

>What's needed is someone on the Fox Team or assigned by the Fox Team to be a watchdog on MSDN. If something can be done by VFP, and it's a generic Visual Studio article, then VFP should be mentioned, if not have some examples posted. If that happened, I believe, more and more developers would be up to speed on what VFP could do. And more novice VFPers would be better informed

This is what I am trying to get at. What can be done about it? We all know the issue (well those of us that have read the 70 threads on VFP's death in the past 6 months *s*) I am looking for something I (we) can *do* about it.

What if we suggested ideas like yours to someone at MS (all of us, ala the MVP demise response)?

No there aren't a lot of us vs. VB programmers (some of us are in both camps) but we are *still* MS customers don't forget, and so are our clients. I don't think inserting three little letters into their press releases is going to break the MS marketing budget. Maybe if we ask them to they will.

Thanks for the feedback John.

Bill