John,

>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.

Bringing developers up to speed isn't the *biggest* issue here -- it's the IS managers and even small-business owners who read the official MS statements of direction in MSDN materials and MS Press books, and read what the computer-oriented press writes, which is taken directly from MS's "official" materials.

It becomes self-propagating. Including "or Visual Foxpro" in MSDN articles would make a *huge* difference in perception, since it would also be included in comments quoted by the press. Editors are notoriously lazy and need to spoon-fed. Probably no one in the press will pick up on "Visual Foxpro" in the project manager screen shot, although plenty of non-VFP developers are probably noticing and saying "Isn't that funny! Can you believe that?".

I also wonder how many people in the press have noticed the absence of Visual J++ in the screen shot.