>>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.


Well, the problem is Microsoft......
All their ActiveX containers do not fully support the specs. So you end up with Access, VFP, C++, VB acting differently when hosting ActiveX controls !!!

As for the vendors:
The largest market is VB so they tend to ignore the other containers because it would require too much testing.