>>Unfortunately Michel, in this particular instance it is VFP that is not standard. - After some lengthy dicussions with Distinct I have found that MS have refused to take VFP 5.0s OCX compatability to same level as VB 5.0s.
>
>I'm sorry, I can't agree with this.

I have to say that I have come to the same conclusion. VFP can't use ActiveX DLL's fully that are created in VB or VC++ (or whatever for that matter). Also, I have run into cases where ActiveX controls don't work as they should under VFP. I have never had such a problem in Visual Basic.