>To me, OOP has little to do with "RAD", especially when I read the virtually all here who do lots of VFP with their own (or bought, I suppose) frameworks tend to make a copy of their 'base' framework classlibs for each separate project. At the very least that suggests some apprehension regarding the quality of their 'base' classes. This also obviates the benefit of inheritance, since each separate project would have to have their specific classlibs 'upgraded' and the project re-compiled in order to implement desireable changes.

Well, inheritance is still a benefit within each project. That is the bottom line on that point.


>
>Many here wish for "intellisense". Isn't that a prime 'component of "RAD"?
>

Sure, it'd be nice to have in VFP. One point for VB.

>I have a long way to go yet before I can claim any proficiency with VB, but at least now having seen some of it, it is nowhere near as bad as I had been led to believe.

I was never led to believe that VB was bad. It has its weaknesses as does VFP. You just see those weaknesses mentioned in arguments based on "What's better, VB or VFP?"

VFP has strengths and weaknesses. So does VB. Neither is better overall. It has to be decided on a case-by-case (app-by-app) basis.

BTW, OOP is a strength of VFP, whether or not other developers use it the way you would like them to use it. I don't think OOP is as much of a benefit to RAD as it is to easier on-going maintenance/enhancements.

Take care,
Joe


>
>Cheers,
>
>Jim N
>
>>Hi Michel,
>>
>>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.
>>
>>With tools like FoxExpress, I could employ many RAD Techniques in Fox 2.x.
>>
>>I just don't understand the conclusion you are making here.
>>
>>I could easily make the argument that in some respects, VB supports RAD better, Intellisense, better Windows API Integration, etc.
>>
>>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.
>>
>>
>>
>>
>>>>3. VB owns 80% of the rad tool's market. Somehow, 80% if the developers out
>>>> there are not casual users. This only goes to support point one above.
>>>
>>>That's an interesting point. I thought we couldn't use VB to do RAD. I used it at several occasions so far and I found it far from being a RAD tool. I searched for RAD product and couldn't found one either. It's true it might be difficult to do RAD as we do it in VFP as it is object based.