>I can remove it from the OCX and have the developers take care of it from their form but this is not what I want. I would like to handle it from the OCX level in case the developers forget to add this code.

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.