I've never debated an issue with JVP, and given his track record he's probably right (technically speaking). But I have to raise the question (or challenge his comment.)

I don't remember if VFP 3.0 could do it, but certainly VFP 5.0 and 6.0 can subclass and inherit functionality from other COM objects (written in other langauges). What comes to mind immediately are controls like the Treeview and Calandar from MS. These are written in C/C++ I'm sure.

I have never tried to subclass a control written in VB, and if that is the distinction that John is making (e.g., VFP can't subclass and inherit from a VB COM object??) then I will stand corrected.

But for sure, VFP has had the ability to subclass and inherit behavior from COM controls (written in C/C++) for years.

Guy





>>He also spoke fondly about the new capability of inheriting behavior of other controls not written in VB.
>
>this is the part I really got excited about!
>
>>He inadvertently forgot to mention that the JV product has been doing that for years.
>
>Has it really? I'm assuming your talking about ActiveX controls, and I dont really think inheritance is going on there. Sure we can access PEMs in VFP, but they dont come up natively in the property sheet. I wasnt really sure and this comment sparked my interest, so I passed it to JVP for comment since he's the one that brought media clip to my attention to begin with. What follows is Petersen's remarks if your interested...
>
>> VFP has NOT done this for years. Sure, VFP has inheritance, but
>> only in the
>> confines of the VFP language. In VS.Net, if something was written
>> in C#, VB
>> code could inherit the functionality. The converse is true.
>>
>> This goes way beyond ActiveX Controls...