Article ID: 202476 - View products that this article applies to.
This article was previously published under Q202476
This article has been archived. It is offered "as is" and will no longer be updated.
When using the OLE control or WebBrowser control on a form in Microsoft Visual Basic to view a Microsoft Word document, you are unable to type any text into the Word document.
This problem occurs if a separate instance of Microsoft Word is running and you switch focus to that instance of Word. When you switch focus back to your Visual Basic form, the Word document in the OLE control or WebBrowser control can no longer be edited.
A workaround for this problem is to activate the Word document in its own Window, rather than using in-place activation. To accomplish this, set the MiscFlags property of the OLE control to vbOLEMiscFlagDisableInPlace, or 2. For example:
Now when you double-click the OLE control, the Word document is activated in its own window inside Microsoft Word. To programmatically activate the Word document in its own window, use the DoVerb method as follows:
Steps to reproduce the behavior
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
If you are using the WebBrowser control instead of the OLE control, the following Knowledge Base article shows how to configure your system so that the Word document is activated in its own window inside Microsoft Word:
162059For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/162059/EN-US/ )Office Documents Open in Internet Explorer
(https://support.microsoft.com/kb/191615/ )BUG: Menu disabled in application activated using OLE control
(https://support.microsoft.com/kb/243392/ )Document opened in Internet Explorer appears inaccessible; exception AV may occur