> 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.