>Why does the fact that VB being object based make it less of a RAD Tool? It's interesting, many folks jump on the OO aspect of VFP when comparing to VB. Yet, if you looked at many of the apps those folks write - many of them are'nt really OO anyway.

I agree. It's true that when I approach VB, I tried to establish a framework based on my VFP framework. Since it is mostly based on OO, that's why I faced a wall. My experience is that I had to keep it simple and avoid those fancy sub classing, etc.

IMOH, an OOP environement certainly contributes to a better RAD development and to have many RAD 3rd party products as we have for VFP.

>I think many folks have issues with VB because they do not know how to use the tool. If you attempt to take a VFP mindset to VB ,you will run into problems. The same would be true for VB developers trying to use VFP.

This is what I faced. I've been using it for a few purposes so far. I don't have that much experience with it. However, it's true that I tried to implement the way I was working with VFP and that was not the good approach to take.


If I would have used VB for non database needs, then I would have feel much better with it. But, coming from VFP, I was kinda shocked with VB.