CreateObject("Outlook.Application")

[Guest]

Hello again,

I have a few machines that have a problem, where the rest don't. Those that
have a problem get the following error msg:

======
Automation error
The specified module could not be found --2147024770
======

when trying to execute the following line of code:

-------
Set objOutlook = CreateObject("Outlook.Application")
-------

All the machines have Office 2003, with a reference to the Microsoft Outlook
11.0 Object library. I thought maybe the library on the problem machines was
corrupt or something, so I had them deselect the reference, copy the
msoutl.olb file from a "working" machine, then re-instate the library
reference. No luck.

(I have a "Dim objOutlook As Outlook.Application" line just before the "Set
objOutlook..." line.)

Any ideas?

 

[Guest]

Clutching at straws here but do they all have Outlook installed in the same
folder location? Do you also have a reference to stdole2.tlb (OLE Automation)?

Steve

 

[Guest]

Steve,

(That's how I feel - "clutching at straws"!)

Anyway, I checked, and, yes, the problem machines have the OLE Automation
reference and have MS Office installed in C:\Program Files\Microsoft
Office\OFFICE11.

Any other straws?!

April

 

[Guest]

Couple more straws...

Have the machines been rebooted since installing Office 2003?
Have you tried re-registering the library on those machines?

Steve

 

[Guest]

Steve,

Rebooted - yes. "Re-registering the library" - sorry, don't know what that
means (other than unchecking the reference in Access, then re-selecting it,
which has been done). How do I re-register the library?

April

 

[Guest]

Do the problem machines have the latest service packs and updates?

Can you copy the MDB to those machines, open the code windows and check for
missing references?

Not sure if it applies to a .olb file but you may want to do a Google on
'Regsrv32'.
You usually use this to register/un-register .dll and .ocx (ActiveX Control)
files...

Steve

 

[Guest]

Steve,

They have SP2 for Office 2003; I already asked them to check the updates and
am awaiting a response. We already checked for "missing referenced" at the
same time we checked for the OLE Automation and Microsoft Outlook 11.0 Object
Library, there are none "missing".

If "updates" are up-to-date and there's still a problem, I check into the
Regsrv32.exe
for possibly registering the .olb

Thanks for your continued/prompt responses. I'll reply again if I'm still
stuck.

April

 

[Gina Whipp]

Another straw...

Are they all using Microsoft Outlook?
Or are some using Outlook Express?

If it works with one and not the other that might be the issue. I found
this to be a problem at one of my Client's and I forget what I did to fix it
but if that is the case I'll attempt looking it up (hunting thru old
databases).

 

[Guest]

Gina (& Steve),

First, I'm not really a big Forums user, so I don't really know how the
"Reply" works in terms of if I "Peply" go the last message in this thread
(which happens to be from Gina, does Steve from prior messages also see this
(or get notified), or should I do a "Reply" to Steve's last post as well?!

Anyway, I wanted to provide follow-up on this thread. A re-install of
Office 2003 on the "offending" machines fixed the problem. I'm glad it's
fixed, but I also kinda wish I knew exactly what the problem was. Anyway,
Gina - I wanted to thank you for your willingness to dig back through the
archives if necessary, and Steve - thanks for all the "straws".

April

 

[Gina Whipp]

April,

No matter which message you reply to we ALL see it, so it is not necessary
to REtype to everyone that offers a suggestion.

Glad the reinstall helped but I agree, would have been nice to know what
initially caused the problem and... your welcome