PFMJI But I wanted to add a nuance to this.

IMHO we ideally should see VS as a toolbox. Need high performance system integration, or device interface type COM components? Fire up C++. Need Data centric biz objs that can act as a database liaison, or cache and manipulate your data? use VFP. Need easy access to the WinAPI, or OLE aware apps (like say Crystal for example) use VB, etc.

I think you are right on target Rox, this whole VB vs. VFP vs. C vs. whatever is outdated in the Component oriented, distributed environment that we are *all* playing in now--whether you are actually writing this kind of code or not. We need to look at the big picture, not just our little corner of it.