>>I don't know VB, so, I can't tell you why it doesn't work.
>>
>>Why don't you want to make a usual ActiveX control in VB? Is there any limitation if you do it?
>
>Well, there are several reasons. First, this isn't a control. Second, if I wanted to deploy my ActiveX DLL on Transaction Server, it couldn't be a control. Third, there are a lot of other ActiveX components out there that I'd like to be able to access from Visual Foxpro (ex. DirectX components).

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?

>Everything works fine, except for being able to trap the events.

So, do you bypassed the OLE error you had?

Vlad