< snipped >
>FWIW, I instantiate ActiveX objects programmatically as often as possible. Dragging and dropping ActiveX objects onto forms creates dependencies on that version of the ActiveX, if I remember correctly.
>
>HTH,
>Jon

Jon,
This is good technique (one which Doug Hennig highly recommends for the reason you stated). However, the problem here (as I see it) is the creation of an ActiveX control created in VFP and used elsewhere (in this case ASP).

If it were being done entirely in VFP, then you could instantiate the ActiveX control, instantiate a VFP object that has the same events and use VFPCOM to bind them. If it were being done with VB, you could DIM a variable using the WithEvents clause and bind the events to a custom object that way. Either way is version independent.

The environment doesn't lend itself to either of these. I don't think VBScript offers event binding (I may be wrong) and using VFPCOM to bind to an object within itself won't work either.