>>The following request for comparison is posted here by permission
>> Perhaps Jay could be CC'd in your message, since he may not be a member of the UT.
>
>Here's my contribution:
>
>I am working on a current project right now. Because of the corporate direction, we are forced to do it in Visual Basic.
>
>When come time to manipulate data, I would say this is where Visual Basic faces a wall. Several developers have spend several days to investigate various controls in Visual Basic, for a data grid, to be able to offer users a pick list. The same was done in Visual FoxPro in 5 minutes when I put it in my framework. I also modified my framework to be able to define an OLE public class in order to have my Visual FoxPro framework grid class to run in Visual Basic. That was done in 2 hours. I built a 350,000 records table as oppose to the 10,000 records we are using in the data bound control in Visual Basic and the Visual FoxPro ole class was still the fastest.
>
>I also faced a wall when I wanted to benefit of OOP in Visual Basic. I rapidly found that there Visual Basic is object based and everything is in the same level. So, the design time in Visual Basic, is extremly important as it may have a major impact of changing something later on during the project. You can't subclass a class as it is not OOP.
>
>The properties sheet does not support a hierarchy. Everything is on the same level.
>
>All the code is in one big chuck of code. The code is not bound to its object. Also, when clicking on a control to get access to the code, you will obtain some inserted lines for the function definition which also include End Sub. All the time, I have to delete what was inserted by Visual Basic. Also, those function definition and the End Sub are a waste a time. Well, I guess this is needed as the code is not bound to its control.
>
>As oppose to Visual FoxPro, you have to define which OCX should be available to your application. You can't have access to an OCX directly from the toolbar at first.


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.