>One definite reason is that threads like this keep being brought on by those who know and those who are quick to jump to conclusions.

>Just look at the "VFP - dead man walking" thread after this one...

I don't think that threads here at UT are what is causing the VFP is dead rumors in the general public. If you look back at the 70 or so threads (including the VFP -dead man walking) over the past few months, they are generally people coming *here* to ask or enumerate their belief that FoxPro is dead. I would say if anything, the majority of the people here are in the business of debunking the rumor, not propogating it.



>And here I am participating in another one...

The point of this thread is NOT to propogate a rumor, but to suggest that the lack of comments that include VFP in MS literature (lke MSDN) are a big source of the problem.

My comment was simply that if MS would take the simple step of including "VFP" between "VB" and "VC++" in sentences like: "Visual Studio via tools like VB, and VC++ is a great platform for developing custom COM components." (I made that up, but you get the idea), then maybe people wouldn't come here all the time, and ask if VFP is dead.

My suggestion is we *as a community* lobby MS to change this practice, since we are MS customers. That's all.

Best,
Bill