>VFP 6.0 is being made to hold onto current developers of Foxpro, FPW ,and VFP.
>That is the unwritten rule that i suspect is being adhered to when you get this "promote VFP yourself" stuff. Full time VFP developers don't have the ability to promote a tool to non-VFP developers. Basically by asking you to "promote VFP yourself" this satisfies Microsoft's overall goal of holding onto current FPD,FPW, and VFP developers and code , and at the same time this stops VFP from directly competing with VB.
>
>These marketing omissions will just keep on happening because there is no way MS will have one of their own products directly compete with VB.
>
>of course by making it "our responsibility" to promote VFP it is then "our fault" if VFP does not climb to unprecedented levels of popularity ...
These words may lead to the conclusion that
- since M$ won't advertise VFP over VB and
- since M$ expects us to promote VFP
then
- we are implicitly expected to promote VFP over VB
May logic may fail, depending on the wind...