IE7 and the Internet Browser control in Microsoft Access

[Ron Hinds]

Before anyone suggests it, I'm fully aware that this is not an IE NG. My
problem concerns compatibility between the Microsoft Internet Controls
(SHDOCVW.DLL) in Access and IE7. I've observed the problem in two different
versions of Access - 97 and 2003. My app uses the Browser Control on the
default SubForm that is displayed when a user logs on. In the 97 version, as
soon as the subform loads an error message appears that reads Access has to
close, Send Error Report etc. If you click Send Error Report, a message
comes back that reads Click Here for Information about this error. This
opens a browser to the Microsoft website where you are informed that Office
97 is no longer supported by this app. In 2003, the app just crashes; no
explanation is given by Send Error Report. I should mention that the app is
developed on a Windows 2000 system that has IE6 installed on it. We
distribute it with the Access Runtime.

 

[Guest]

I am also experiencing this problem too in an Access 2003 (not runtime) MDB
or MDE. I was able to work around it by first displaying a new form with a
webbrowser control without specifying an url. Then clicking a button to
invoke WebBrowser9.Navigate2 "somewebpage" did display the page. After that
my original form works as it did before (so far) and was able to open a
locally saved webpage upon opening the form. However if I exit Access and try
my original form without using my new blank browser form first, Access will
crash again. I will continue testing but I am open to suggestions for a
better solution.

 

[Ross Crawford]

I have a similar problem with Access 2000 SR-1. My form displays fine,
and all other functions work, but when I click a button that does a
browser.Navigate "URL", Access shuts down with no "send information to
microsoft" button.

I also just upgraded to IE7, the form was originally developed with IE6.

ROSCO

 

[Ross Crawford]

Update:

I uninstalled IE7, and now when I click the button, half the page loads,
then Access gets the error "Object required" on the line that calls
browser.Navigate. Choosing Yes or No the page loads completely, and I
can continue.

And occasionally when I close that database, I still get the "Access has
to shut down error", but I can't duplicate the circumstances.

Thanks Microsoft, for hobbling a perfectly working application. I can't
wait to see what else on my system isn't working now. So much for
"critical updates". Please include a warning in future "This critical
update may cause other Microsoft applications to suddenly start behaving
strangely, or even stop working."

ROSCO

 

[Ron Hinds]

Here, here!

Update:

I uninstalled IE7, and now when I click the button, half the page loads,
then Access gets the error "Object required" on the line that calls
browser.Navigate. Choosing Yes or No the page loads completely, and I
can continue.

And occasionally when I close that database, I still get the "Access has
to shut down error", but I can't duplicate the circumstances.

Thanks Microsoft, for hobbling a perfectly working application. I can't
wait to see what else on my system isn't working now. So much for
"critical updates". Please include a warning in future "This critical
update may cause other Microsoft applications to suddenly start behaving
strangely, or even stop working."

ROSCO

 

[Bill Mosca, MS Access MVP]

I'm one of those guys who does NOT need to have the latest, greatest version
of any software, especially something like IE.

I say let the other people mess with the buggy stuff. I'll install IE after
at least the first SR comes out.

Unfortunately, if you develop for independent clients, they might buy your
database app and then install IE7 and shred your app while blaming you for
not doing a good job.

 

[Ron Hinds]

I'm one of those guys who does NOT need to have the latest, greatest version
of any software, especially something like IE.

I say let the other people mess with the buggy stuff. I'll install IE after
at least the first SR comes out.

Unfortunately, if you develop for independent clients, they might buy your
database app and then install IE7 and shred your app while blaming you for
not doing a good job.

That's EXACTLY what happens, Bill. They don't think to blame Microsoft since
IE7 works otherwise. The worst part is that IE7 is being touted as a
"Critical Update" by Microsoft. So our clients, who don't know any better,
assume that they need it. So now I'm forced to develop two separate versions
of my app to distribute and keep in synch. Thank you Bill Gates!