>>1. VB is NOT object oriented, while VFP is. That means VFP has inheritance,
>>while VB doesn't have it.
>Do you really think that inheritance, by itself, is sufficient reason to use
>VFP over VB?

I think it depends on your user interface. If you have dozens of forms, and hundreds of controls, the answer is "Hell, yeah!" If you have something like a newsreader interface, inheritance doesn't gain you much on the UI, and the business objects are more likely to be COM, which doesn't yet support inheritance.

Do you think this is on-track, John?