Currently, I have an ActiveX DLL generated in VB 5.0.  This DLL is
used by an MDI application written in VB 5.0.  The GUIs produced by
the DLL don't let me use the MDI Child property on the forms.  This
means when you bring up the DLL GUI's and have the app running, it's
like running two apps.  The DLL GUI is either on top of (and active)
or behind the app.  I'd like these GUI's to be contained by the app.
I could easily migrate the DLL stuff back into the app so that its
GUI's are like all other forms of the app, but I really want to be
able to deliver it as a DLL so we can upgrade the portions of the app
embodied in the DLL just by delivering a new DLL.

Obviously, this is a design/architecture problem.  What is the
approach generally taken for such cases?

-----
L. Rodney Ford


"Paranoia is just reality on a finer scale.", Strange Days