>>>>...VFP is so much more object oriented vs. VB.
>>>
>>>Why?
>>>
>>>(I don't know very much about VB...)
>>
>>Because VB is object based not object oriented.
>
>And what's the difference - object based vs object oriented? Isn't it possible to create classes in VB? Or maybe to develop frameworks?

Classes in VB are very different from classes in an OOP language. You need inheritance, polymorphism, encapsulation and all that other stuff for it to be OOP....VFP has all this....VB doesn't. Here's test for you: Launch VB, create a class and then subclass it. Nope can't do. Test 2: Try to subclass an ActiveX control in VB...nope fails again....Test 3: Create a form in VB. Create another form based on the first. Now change the background color in form 1 and form 2...Requires 2 changes...one on each form. TO do this in VFP, create a form class and create a second form from that class....then change the background color. Imagine if you had a system with dozens or hundreds of forms....

VFP wins this contest hands down.