>This is one of those touchy things about creating ActiveX controls. In theory, it is a bad thing to alter the parent of the OCX control. Now that doesn't mean that it sometimes can't be done, but the thought is that you may not know where your control might get used and how the container will handle the action.
>
>In an application that I've written recently we do a lot of interaction with the parent, but they are UserControls within the app, not seperate ActiveX controls.

I found that as well. I think the best is to let the developers to decide if they want to let the user do something else when something is run from the ActiveX.