BUG: Cannot edit Word document in OLE or WebBrowser control

Please follow this link and have a look

They are suggesting following workaround.

Quote:

---

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: OLE1.MiscFlags = vbOLEMiscFlagDisableInPlace

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:

OLE1.DoVerb vbOLEOpen

---

But there is no MiscFlags property or DoVerb method for WebBrowser control. How to implement this workaround for WebBrowser control.

anyone

what about trying to load it directly into word?

strange.. when I just tried opening a doc in the webbrowser control I could edit it no problem?

Actually i am developing an application where i load word file in webbrowser control and manage from there. But i am now facing this problem.

Quote:

---

Originally Posted by [A51g]Static

strange.. when I just tried opening a doc in the webbrowser control I could edit it no problem?

---

Load a file in webbrowser control then start word and get back to webbrowser control. you cannot edit the document or there right click menu will be disabled.

i dont get a right click to start.. but doc is still editable?

I would still suggest using word.. then u can have full control

Actually you can edit the document in webbrowser control while another instance of word is running but you don't get the right click menu that shows cut,copy,paste,spelling/grammar suggestions etc. That is where i am stuck on.

ahhh... gotcha. sorry.. ive never run into this.. so im not sure what the issue might be.

but, why not just load it in word itself?

In my app I am doing stuff that MS Word don't provides. I know VBA is also the way but the app i developing is going to be deployed on 150+ machine and u know we cannot provide autoupdate feature here. And another reason why i am not going for vba is the app was already developed and i am developing it furthur.

VB Code:

Dim temp As Word.Application
        'Test if object is already created before calling CreateObject:
        If TypeName(wrdApp) <> "Application" Then
            temp = CreateObject("Word.Application")
            ' wrdApp is declared below Windows Froms designer generated code
            ' dim wrdApp As Word.Application
            wrdApp = CreateObject("Word.Application")
            temp.Quit()
            temp = Nothing
        End If