According to Jim Duffy, the problem is that VB (he didn't mention vc) is not particularly finicky about activex controls meeting the specs precisely, whereas vfp is.

If something's not entirely kosher within the activex control, it won't work with vfp.

Alex


>>I'm not certain what they mean by "True ActiveX" either.
>
>I would take it to mean "whatever works in VB/VC++". There is no "True ActiveX", AFAIK. However, there is no standard for ActiveX containers. IOW, the VB/VC++/VFP developers were free to design their containers any way they wish, just as long as they worked. The end result was that control developers do some funky things, test them against VB/VC++, and once they get it to work, they're done. Unfortunately, VFP is often left out of the testing picture, so some controls such as the Coolbar may not work in VFP.
>
>In summary, what the company is really telling you is that they didn't bother to test their control(s) in VFP.