Re: Error triggered by navigation
- From: JonWayn <JonWayn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 9 Feb 2008 18:53:00 -0800
I finally found a solution to that problem. Instead of using the WebBrowser
control on a form, I am using the InternetExplorer object. It has all the
same properties and methods, so there was little changes needed. Works fine.
Thanks for your input.
"Leslie Milburn" wrote:
.
"JonWayn" <JonWayn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0B9E35C6-645C-4E36-8B4E-7A6DC482E13A@xxxxxxxxxxxxxxxx
Before I even read your reply, I went in a unchecked "Disable script
debugging (IE)". The other one wasnt checked. So I left them both
unchecked
and tried running my program again. It didnt solve the problem. After
reading
your response, I went back in and checked them both. Now I get a slightly
different box, just as frequently nonetheless.
I have no control over the contents of the website. Also, if I open IE and
use the website from the user interface, I do not get those errors.
Jon,
You may need to implement IOleCommandTarget and in particular the Exec
function where you can intercept the command which displays script errors by
default. Heres a code snippet:
HRESULT STDMETHODCALLTYPE Target_Exec(IOleCommandTarget FAR* This,
const GUID __RPC_FAR *pguidCmdGroup,
DWORD nCmdID,
DWORD nCmdexecopt,
VARIANT __RPC_FAR *pvaIn,
VARIANT __RPC_FAR *pvaOut)
{
// See docobj.h for OLECMDID values
if (nCmdID == OLECMDID_SHOWSCRIPTERROR) {
V_BOOL(pvaOut) = VARIANT_TRUE;
return S_OK;
}
return OLECMDERR_E_NOTSUPPORTED; // Let the default handler have it
}
Leslie.
- References:
- Re: Error triggered by navigation
- From: Leslie Milburn
- Re: Error triggered by navigation
- From: JonWayn
- Re: Error triggered by navigation
- From: Leslie Milburn
- Re: Error triggered by navigation
- Prev by Date: Re: Error triggered by navigation
- Next by Date: Re: WebBrowse and Word/Excel 2007
- Previous by thread: Re: Error triggered by navigation
- Next by thread: Re: WebBrowse and Word/Excel 2007
- Index(es):
Relevant Pages
|