Ron,

>I would not recommend subclassing the OCX directly. A). It places the license file into every VCX or Form you drop the OCX directly into B). as well as the GUID C). from what I have been told by several OCX vendors the design specs for OCX's are such that subclassing of the OCX was not accounted for, it causes problems in some areas. I have never done it so I don't know. I subclass my containers.

I knew it was problematic, thanks for the additional detail.

I think I'd put all the customization code in helper methods of the container that holds the ActiveX. That way the only code you have to put in the ActiveX methods are calls to your container helper methods. This would minimize duplicated instance code.


>I would like to see an initiative whereby we as a development community develop a public domain framework for this kind of thing for VFP. I would have a whole lot to contribute. My fear would be that 7 fixes all of this and the framework need would go by the wayside like genscrnX. If it does not maybe it will be a good idea.

I'm not sure you could herd too many VFP developers in the same direction, especially with 3rd party ActiveX controls. This discussion would make for some great articles over on the W i k i under the ActiveX topics.