P
Peter Karlström
I have developed an OCX-control in VB6, in which I control a word-session.
The OCX is used to open word-documents from another application, and also to
place the window docked with the mentioned application window, or to
maximize
the Word-window depending on "type of document".
The control works like a charm on Word XP (version 10), but on Word 2000
version 9.0.x) we have som serious problem.
If the user closes the word application manually, the control automaticly
starts a
new word session. But in some of these new sessions all commandbars and also
the menubar is missing.
I have debugged the control, but regardless how I try to manipulate the
window by
enabling CommandBars.Activemenu and make CommandBars.Visible = true nothing
seems to affect the Word-session.
If I close the application (and the Word-session with it), I starts word
again, the menu
and the commandbars are there again.
On Microsofts KB I found som articles regarding this error but none of them
is helping
me solving this problem.
Is there anyone out there who knows how to tackle this bug?
Thanks in advance
Peter Karlström
Midrange AB, Sweden
The OCX is used to open word-documents from another application, and also to
place the window docked with the mentioned application window, or to
maximize
the Word-window depending on "type of document".
The control works like a charm on Word XP (version 10), but on Word 2000
version 9.0.x) we have som serious problem.
If the user closes the word application manually, the control automaticly
starts a
new word session. But in some of these new sessions all commandbars and also
the menubar is missing.
I have debugged the control, but regardless how I try to manipulate the
window by
enabling CommandBars.Activemenu and make CommandBars.Visible = true nothing
seems to affect the Word-session.
If I close the application (and the Word-session with it), I starts word
again, the menu
and the commandbars are there again.
On Microsofts KB I found som articles regarding this error but none of them
is helping
me solving this problem.
Is there anyone out there who knows how to tackle this bug?
Thanks in advance
Peter Karlström
Midrange AB, Sweden