IE.ReadyState not working with MS Office 15.0 Access DB engine obj lib

otanilon

New member
Local time
Today, 20:06
Joined
Jun 13, 2014
Messages
4
Hi Experts,
I have an MS Access 2010 DB with running successfully on a number of machines. I recently tried to run the same Access DB on a new machine and I am encountering a problem. I narrowed down the problematic code :

Code:
    Set IE = CreateObject("InternetExplorer.Application")
    IE.Visible = True
    IE.navigate url
    While IE.ReadyState - 4: WaitTime (1): Wend

on the problematic machine, IE.ReadyState is not functioning.

I compared my successful environments with the new environment and I see 4 differences:
(1) windows operating system (7 vs 8.1)
(2) other versions of Office installed (none vs Office 2013)
(3) version of MS Office Access DB engine object library (14 vs 15)
(4) Version of Access 2010 (English vs Japanese)

I thought #3 was the most suspect. So the next logical thing to do I thought would be to uncheck the MS Office 15.0 Access DB engine object library in my problematic environment (easy). And then check the MS Office 14.0 Access DB engine object library. However, I do not see the MS Office Access DB engine object library in my list of references. How can I get the 'MS Office 14.0 Access DB engine object library' in my list of references? Does anyone know where I can find this file?

Any guidance would be greatly appreciated.

Thanks,
Lon
 
You forgot the most essential bit: what the heck is "not functioning"? It's like writing "my butt is not itching" - not much info in that, :D
 
Sorry for the lack of clarification.
I mean IE.readyState seems to have no value.

For example, in the working environment, if I debug.print IE.readyState after the object is created, it will usually show me a value (between 1 and 4). However, in the non-working environment, it never seems to have a value.
 
Sounds strange. Tyr this
Code:
    While oBrowser.Busy
        DoEvents
Wend

before your test.

Also, a more common formulation would be

Code:
While IE.ReadyState <> 4

but that is irrelevant so long as it has no value to test.
 
Hi Spikepl,
Thanks for your help.

I tried the following:
Code:
While oBrowser.Busy
        DoEvents
Wend

It went into an endless loop and did not proceed any further.
I did not define oBrowser before the above code.
Looking at the local window in the debugger, oBrowser is Variant/empty type with no value.
 
I would like to see if the application would behave differently if I could get 'MS Office 14.0 Access DB engine object library' loaded and unload the newer version. But I havent yet figured out how to do that.
 

Users who are viewing this thread

Back
Top Bottom