>Jim,
>
>>But for other OOP aspects, VFP is far ahead of VB6 and considerably behind VB.NET.<
>
>Nope, wrong about VB.NET's OOP capabilities. VFP is still ahead in that respect. There is no inherent concept of visual inheritance. In other words, in VFP, you can easily design a container class and drop it on a form and manipulate it's objects ... visually move the objects contained in the container in that instance of the container on the form. You can change properties of objects in the instantiated container also. Can't do this in .NET. You can jump through a few hoops to expose all the objects in your "container" class (.NET calls them UserControls) as properties so that you can at least tweak the properties in the instanciated control on the Property Sheet, but there is absolutely no way to visually move those objects around once you've dropped the control on a form. That really sucks, IMHO.
>
>~~Bonnie
>
>
"Sucks" sounds about right.

There are, though, things that VB.NET can (apparently - only from reading, not doing) do that cannot be done in VFP.

Things like:
- static variables;
- execute method code without instantiation;
- method overloading;
- I guess there's more...

I must admit that, in my little head, these things seem distinctly NON-OOP yet nevertheless they seem to be written about as added OOP facilities of VB.NET.

Someday I'll have some practical experience under my belt and will be able to talk more knowledgeably on the subject.


>>I'd say that the instructor needs only to ask himself one question to answer the question for himself... why has VB changed so much with the "7" version (.NET) if it is so far ahead of VFP from a OOP perspective?
>>
>>VFP cannot 'expose' (if that's the correct terminology) EVENTS of its OWN MAKING whereas VB6 can. But for other OOP aspects, VFP is far ahead of VB6 and considerably behind VB.NET.
>>
>>
>>
>>>Hi All,
>>>
>>>I'm currently retraining in E-commerce taking Visual Basic 6. My Instructor keeps insisting that Visual Basic is miles ahead of Visual Foxpro and will remain that way. From what I've seen todate Visual Basic wants to hide everything properties/methods/events from developers and only expose what they want. Does Visual Foxpro have the same capabilites and taking a step back first, why is it such a big deal to hide things in the first place ?
>>>
>>>thanks,
>>>
>>>Don