>> People don't just switch development tools that easily.
>
>There's an understatement. Religious wars have been fought over code editors alone.

I think the best way to get someone to switch from some product to using Visual FoxPro is to actually sit down with that person and show them the product, then let the feature set of VFP 7 sell them and get them to convert. Also showing working solutions created with VFP. This is where the FoxPro community can help greatly, find developers using products like PowerBuilder, Delphi, Clipper, and even FoxPro 2.x/3/5/6, and take the time to convince them to move to VFP 7.0.

While myself and the Fox team actively educate people about VFP 7.0 to the VFP community, outside the VFP community, and also within Microsoft, we need the FoxPro community to contribute back by having individuals take the time to get other Fox developers using VFP 7.0 and finding potential candidates to switch to VFP. This is what makes the FoxPro community great. While a new and improved feature of VFP 7.0 is extended VFP marketing, the best feature of Visual FoxPro is the FoxPro community itself.