MDI Child in ActiveX Dll

I need to have MDI Form in Standard Exe and MDI Child form in ActiveX Dll.

On Creating an object of a Class in ActiveX dll and thereby loading the MDI Child form, the child form does not recognize the Parent MDI Form in Standard Exe.

How to solve this?
Who is Participating?
_jkAuthor Commented:
Adjusted points to 75
Éric MoreauSenior .Net ConsultantCommented:
There was an article about that in VBPJ (march 99 I think) from Dan Appleman.

He suggested:
-building ActiveX control for each  child form;
-add an empty child form to our main project;
-instantiate the control on the empty form.
_jkAuthor Commented:
Thanks Mr emoreau.
But this ActiveX Component Dll is going to have many other functionalities other than MDI Child.  
So I am not sure whether it will be suitable to put it as ActiveX Control.

Éric MoreauSenior .Net ConsultantCommented:
Why not! One of the main differences between ActiveX DLL and ActiveX OCX is actuallay ... the extension!!!

No, let's be serious now.

The main difference is that ActiveX OCX are "normally" something with an interface to the user. I say "normally" because there are cases (think about the Timer control) which is not visible by the user but easier to use by the programmer.

Both are in-process (so no difference of performance between both).

Your ActiveX control can contain classes so I don't see what the DLL can contain that OCX can't.

I think that I have the sample code of VBPJ. Let me know if you are interested.
All Courses

From novice to tech pro — start learning today.