D
David
I'm using the AxSHDocVw.WebBrowser control to download data from a webpage
at work (it's an internal page on my company's intranet).
The page produces a runtime error after a while and the strange thing is
that until the page is refreshed with Internet Explorer, the error keeps
occurring. I realize no one can debug an application that I can't even
provide details about (I didn't write nor do I have access to it) but what
difference would it make if I used .Refresh with the WebBrowser control
(I've also tried the other WebBrowser control in the toolbox) versus
refreshing with IE? I can refresh IE on the computer the VB program is
running on or any other computer on the network- either option stops the
page from returning a runtime error. I've even tried creating a second
control to refresh the page after the error starts occurring but this has
not helped at all.
Any ideas?
(Using Visual Studio 2005 / VB. The page is coded in VB2005/ASP.)
at work (it's an internal page on my company's intranet).
The page produces a runtime error after a while and the strange thing is
that until the page is refreshed with Internet Explorer, the error keeps
occurring. I realize no one can debug an application that I can't even
provide details about (I didn't write nor do I have access to it) but what
difference would it make if I used .Refresh with the WebBrowser control
(I've also tried the other WebBrowser control in the toolbox) versus
refreshing with IE? I can refresh IE on the computer the VB program is
running on or any other computer on the network- either option stops the
page from returning a runtime error. I've even tried creating a second
control to refresh the page after the error starts occurring but this has
not helped at all.
Any ideas?
(Using Visual Studio 2005 / VB. The page is coded in VB2005/ASP.)