Erik..

I think you are mis-applying a term of art here. What you describe here and in thread #451752 are ways to create wrapper classes - which BTW, is hardly a revolutionary concept since the technique has been documented extensively. I compare this to calling Access/Assign Methods events. That too was a gross mis-application of terms. while it simulated the desired result, in reality, it was not the real thing and futher, fell short of the real thing.

ActiveX controls are hosted in a container. When you subclass an ActiveX control, in reality, you are subclassing the container - not the control itself. In fact, you never really work with the ActiveX control directly. Don't know if this is a big deal or not. FWIW, I don't think it is. With COM Components, you are essentially doing the same thing.

Wrappers are an effective tool for simplifing interfaces. Dataclas COM is just that - a wrapper that simplifies and manages various ADO objects. To say it is a way of subclassing would be both incorrect and misleading. If it were subclassing, we could choose to override and change inherited behaviors.

FWIW, it would appear that with ADO.Net, you can in fact subclass the various ADO classes.


< JVP >







>>Hi All!
>>
>>Is it possible to subclass a ADO class in a .PRG in VFP6?
>>
>>I am trying to subclass ADODB.Connection and ADODB.RecordSet but have not succeded.
>>
>>TIA
>>/Peter
>
>Check out Thread #451752. You should be able to use this technique to create a 'subclass' of the connection and Recordset objects. If you need to write code in events, you should be able to combine this technique with the VFPCOM utility to get most of the functionality you need.