>>>When you said "Bindevents works with any class whether it was created programmatically or visually" I thought you meant that it could be
>>>created by placing it "visually" on a form.
>>
>>It means that only the receiving control. It may be any VFP object and placed on the form visually or programmatically.
>
>I'm sorry Nick but you've lost me... At first you said "BindEvents does not
>allow to bind native VFP objects. I think it may treat ActiveX as VFP OLE
>control, considering it as VFP object."
>
>Then you said... "It may be any VFP object and placed on the form visually or
>programmatically."
>
>These two statements seem to contradict each other.

Not really, :) as I am talking only about the receiving object.
Typically, when you do BindEvents, only the receiving VFP object is the ONE which is VFP object placed on the form. The COM is supposed to be "outside" the form. In case if it is a DCOM, it even physically is running on a remote server. The form may have the property referencing the COM/DCOM object, but it does not mean that COM is physically placed on the form.

Note, that even receiving object does not have to be placed on the form. It may be just created with CREATEOBJECT(). All it has to do is to exist and be bound to COM to receive the events.

What you are trying to do is to place TWO objects on the form, one is ActiveX and another one is VFP object which receives the events.