This is kinda a repost, except I am phrasing the question in a different way
since I have a better idea what the problem is now.
We are using the DSOFramer ( http://support.microsoft.com/?id=311765 ) in
our just about released project. The bug is simple... going to Word
externally and comming back to our embeded Word control results in the
toolbar (or also known asa CommandBars in the automation document) will no
longer accept clicks.
Built another small sample app up in C# and same problem. Built a project
in VC++ 6.0, and the problem does not exist. Ran Microsofts VB example from
the link above... the problem does not exist.
So my question: is there something about the managed world and unmanaged
world that I am missing? I take it activeX controls written in C++ and VB
are unmanaged... I am a little confused on the subject.
Does anyone see a different way of calling or talking to the control that
would make a difference? Is there a command I can send an activeX object in
general when brining my app back in focus that would clear/ reset/
reinitialize/ prompt the control to reset its controls? I can run a
WordControl.Save(), WordControl.Save(), WordControl.Open() and everything
works again, but that is not the solution as it is slow and makes the screen
flicker... but it does indeed reset the control so things work again.
Thanks for reading this. We look forward to reading your replies.
