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

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.

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