I personally can't stand VB's so called "object" model. Also, I am 100x more familiar with VFP than with VB. What it all comes down to is a comparison of pros and cons. VFP gives you lightning fast native database access, but lots of bloat. VB gives you the most intelligent development environment to date. VFP gives a nice (but not great) object model. VB gives you an imaginary one.

I do see a serious problem with VB in terms of stability and predictability. I am extremely familiar with VFP. I have used it for just about everything it was *intended* to be used for. The problem comes when you try and get it to behave in a specified manner. We've all had our gripes with ther report designer. Grids and other controls that don't behave according to spec, or in an unexpected manner. I have seen VERY little of this in VB. Try to write a database application is more painful in VB, but there is more coding, and less headaches. Thats my impression based on lots of experience and experimentation.

>> 2a) Search the VB forum for messages written since Jan. 1, 1998 containing the word "workaround" (9 messages). Then search the VFP forum for the same (183 messages)
>>
>
>Gino, Gino....sigh.....could 2a) be attributed to the simple fact that, on the UT, there are a trememdous difference in the number of posts? Many, many more VFP posts than VB posts.
>
>All else being equal, a true OOP language used with OOP methods should be much faster to develop in than an equivalent procedural GL....as someone else pointed out in another post:
>
>An application has 20 screens. The client demands ...let's say ... a global font change. I can do it by modifying a few classes in VFP...maybe a 5-10 min change. Recomplile. Viola! In VB...I have a major major retooling problem.
>
>So, maybe *some* of the development time issue has to do with what you're familiar with and how you use it. But a lot of the time has to do with the capabilities of the development environment. VB has no visual classes, little inheritance and/or polymorphism. You cannot save visual objects as classes. When you do something simple such as change an object name, you have to recode your declarations (I won't dignify them by calling them methods).
>
>The day that VB gives me as much OOP capabilities as VFP, I will no longer argue this point with you...until then, I can't be convinced.