VFP offers a number of features superior to VB -- including inheritance, local data handling, better native controls for certain types of interfaces. The next version of VB will narrow, but not close this gap. It is possible the eventually VB will be able to do everything as well as VFP, as easily as VFP. If this should happen --great.

I'm great believer in the right tool for the job -- but if one of tools evolves to the point where it can completely replace the other -- that's a great convenience and well worthwhile. If VB evolves to the point where VFP is no longer needed, that's one less set of syntax to keep up with. In the meantime, I'll use VFP for what it does best , and VB for what it does best.