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

< s >Been there, done that...

Where's the picture Mike?:-)

Enough fun. First, I don't believe the "VFP is more finicky about ActiveX controls than < fill in the blank >" business entirely. One of the reasons that I mentioned the Coolbar specifically was your (MS's, not Mike Stewart's< g >) KB article Q186123. To quote:

"The Coolbar ActiveX control is a container control that consists of a collection of "Band" objects used to create a configurable toolbar that is associated with a form. A Coolbar control typically contains two or more Bands, which the user may resize and rearrange. Each of these Bands contains a single child control. The problems occur because Visual FoxPro can not process the messages from these child controls in the Band; therefore, erratic responses occur. In fact, Visual FoxPro cannot handle any ActiveX controls that support containership."