>I don't understand your 3rd argument. Why would your control stop you from using other ActiveX controls.
>
>>Also, if I wanted to create an ActiveX Exe that could run on it's own, and yet expose an object structure for use in other applications (not as an insertable object) it can't be a control.
>
>But you can develop a control and use this control:
>- in VB to create an ActiveX exe that will expose the control;
>- in VFP as any other ActiveX.
>
>My feeling is that we use the same words for different things. :) Do you mean that in VB an "ActiveX control" MUST be visible?

An ActiveX component is not necessarily a control. A control is something is sited on a container. There are times where you do need/want a container, nor make your component need a container. DirectX from Microsoft is an example of ActiveX DLLs (aka COM Objects). These are not controls, but you can instantiate objects, and you can access properties, events and methods. In VB you have complete access to these things. In Fox (so far) I don't see that you can have complete access to Non-Control objects.

I don't want to focus on MY situation here, because it's an example of what else exists out there, and will continue to grow. I'm just trying to get a small example of some functionality that should work in VFP. But I'm finding that VFP may be falling short in this area.