Kjeld wrote:
> We have created a MDI application that uses a AxSHDocVw.AxWebBrowser
> component on one of the child windows.
>
> As soon as this child window is created, none of the open MDI child windows
> is activated if clicked upon, except for when the window border or title bar
> is clicked.
>
> So the problem is: AxSHDocVw.AxWebBrowser if contained by a MDI child
> window, prevents child windows from being activated properly.
>
> It is even possible to have two active MDI child windows!
>
> I could not find a bug report in support database. Am I doing something
> wrong or is this truly a bug?

"Robert Jordan" wrote:

> Kjeld wrote:
> > We have created a MDI application that uses a AxSHDocVw.AxWebBrowser
> > component on one of the child windows.
> >
> > As soon as this child window is created, none of the open MDI child windows
> > is activated if clicked upon, except for when the window border or title bar
> > is clicked.
> >
> > So the problem is: AxSHDocVw.AxWebBrowser if contained by a MDI child
> > window, prevents child windows from being activated properly.
> >
> > It is even possible to have two active MDI child windows!
> >
> > I could not find a bug report in support database. Am I doing something
> > wrong or is this truly a bug?
>
> In a DocumentComplete event handler you should call
>
> axBrowser.DoVerb(-4);
>
> -4 stands for the OLE verb UIACTIVATE.
> axBrowser is AxWebBrowser instance.
>
> Rob