>Let me add that you can sub class ActiveX controls in VFP, but not in VB and from what I've heard even VC++ won't subclass activex controls. If I'm wrong on this, someone let me know.

And to add more...

In the last month, I've talked with 4 VB developers who started to make a move to Visual FoxPro. They were amazed with its OOP environment, powerful database and have begun their search in using a RAD tool to simplify the move.

Why is it that we can't say the same thing when it is going the reserve way? One answer I got was that Visual FoxPro developers are downgrading from an OOP, powerful database and RAD environment, when starting to do some applications in Visual Basic while Visual Basic developers have the feeling of upgrading to a new environment while they can now benefit of OOP, RAD and Rushmore. For us, it's difficult to adjust to VB because we have to change our way of thinking in relation to OOP, powerful database and RAD.

When I began working with Visual Basic, for the current application, I was trying to subclass and work in an hierarchy way which was wrong. I had to adjust to object based which was now a little bit more easy.

Yes, each environment have their market. But, what is difficult to accept, is when a big corporation need a powerful application which deal with database and to be OOP ready and they try to do that in VB.