PC Review
Forums
Newsgroups
Microsoft Outlook
Microsoft Outlook Form Programming
passing parameters to the WebBrowser control in Outlook Form, (also ReadyState not changing)
Forums
Newsgroups
Microsoft Outlook
Microsoft Outlook Form Programming
passing parameters to the WebBrowser control in Outlook Form, (also ReadyState not changing)
![]() |
passing parameters to the WebBrowser control in Outlook Form, (also ReadyState not changing) |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
I have embedded a WebBrowser control in a custom Outlook contact form
and have code that calls the navigate method to load a local .htm file. I would like to be able to pass a parameter into the .htm file which will help customize what is displayed based on the current contact item. The ultimate purpose being that ADODB will be used in the vbscript of the .htm to create a report based on this parameter. I first tried passing the following to the Navigate method, "C:\SaarIQ\CMReports\default.htm?id=1" But the parameters did not show up in the document.url, not even the "?" I then tried changing the value of a hidden textbox in the loaded .htm file with the following code Set objInsp = Item.GetInspector objInsp.ModifiedFormPages("SaarIQ").WB.document.all.item("txtTest").value = "1234" Which threw a object required error. I then added a do loop to check for the objInsp.ModifiedFormPages("SaarIQ").WB.ReadyState, which resulted in an infinite loop. In troubleshooting this I was able to receive the ReadyState = 4 after a msgbox was used for variable testing. It seems the WebBrowser.ReadyState variable is not changed within an Outlook Form unless I use a msgbox. I am running Office XP - sp2, so I was wondering if this was part of the security patch. Sorry for such a long message, I just wanted to bring you up to speed on what I have currently tried. I would appreciate anyones help in either 1) passing a parameter to the document in a webbrowser control 2) or why the ReadyState only changes with a message box, and if there is a work around for this. Thank you for your help, Jeff |
|
|
|
#2 |
|
Guest
Posts: n/a
|
I solved the first part of my problem.
I was using document.url instead of location.search Any help on the ReadyState value would still be much appreciateded. Thanks, Jeff |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

