>I've been coding in VFP/FP for about eight years and VB about three years. I think VFP is the superior overall product.
>I think Microsoft treats VFP like a step child by not promoting it while they promote VB to the hilt.

I find that to be the case for apps that fit VFP's strengths; for developing data-centric projhects in an OOA/OOD environment, I find VFP to be a much stronger tool. The native data engine and the direct incoporation of record-level and SQL-oriented operations offers significant advantages where it can be applied well. Its OO features make it a strong player in several different roles in the MS/Visual Studio toolset. I find that for the types of apps that I develop with VFP, I'm far more productive, and I'm more likely meet my target deliverables with it; that's probably because I have more experience with it, and the framework and add-on tools help provide a consistently good solution. In many case, VB would require significantly more work to use as the tool for developuibng data-centric apps. And the availability of very knowledgable people throug services like UT is invaluable.

There are places where VB is a more appropriate tool, or C++, and I use them to meet specific needs, the same way I use VFP when it's appropriate. Most of the time I'm hired to design and implement a system, and languages are a secondary consideration.

YMMV; both have their place.