>A few of us stuck with it, though, through those dark days, and now things have turned around considerably. PB had become the main large-app dev tool, but they've had just monumental problems with both the tool itself, and finding good PB developers. VB has gone down the drain as a large-app dev tool after several large systems attempted with it failed. Add to that a few very successful vfp5 & 6 apps, and you have a new perspective even at the top-level here. Not chomping at the bit for it, exactly, but at least being open-minded about vfp now.

The reason why PB has an edged on VFP when it comes to popularity and marketshare is that it has been around since 1990. But when it comes to richness in development feature, I will vote for VFP. Not because I am a VFP user but because PB was my development tool before with Oracle back-end.

The problem mainly is not on the product side, it's on how MS handles it overall.

>
>Being included in VS has been a big factor in getting vfp some new respect, too.