Run time error 430 with late binding Outlook 2003

[-mhd]

I am getting an error report from a user "run time error 430 Class
does not support automation". My application is using late binding to
Outlook 2003 and the following line is the crash point.

Set oObject = CreateObject("Outlook.Application")

I have occasionally over the last year or two solved this problem with
older versions of Outlook by suggesting they reinstall or use the
repair Outlook option from their Office CD. However lately the only
time I get this report is from users of Outlook 2003. Is there a
problem with using established connection techniques with '03 or is it
just that it is most likely the popular version out there?

Any tips for solving this problem?

Thanks
-mhd

 

[Sue Mosher [MVP-Outlook]]

This error is often caused by anti-virus applications whose script-blocking
feature doesn't allow CreateObject("Outlook.Application")

 

[-mhd]

This error is often caused by anti-virus applications whose script-blocking
feature doesn't allow CreateObject("Outlook.Application")

That's interesting. I'll pass that on and see what happens.

I wonder what the proper way to deal with this at run time would be?
Popping a message box saying perhaps you should shut down your anti
virus software isn't going to win me many points with trial users.

Regards
-mhd

 

[Ken Slovak - [MVP - Outlook]]

Where is your code running? Is it a stand-alone app or a COM addin?

 

[-mhd]

Where is your code running? Is it a stand-alone app or a COM addin?

It is a stand alone screen pop software for telephone systems

-mhd

 

[Ken Slovak - [MVP - Outlook]]

And is any script stopper software running on the problem computer? What if
you early bind the Outlook reference, or if Outlook is always going to be
running when your application is running how about GetObject(,
"Outlook.Application")?

 

[-mhd]

And is any script stopper software running on the problem computer? What if
you early bind the Outlook reference, or if Outlook is always going to be
running when your application is running how about GetObject(,
"Outlook.Application")?

Outlook may or may not be running when my telephony application is
launched. Early binding was a headache since my users could have any
version of Office installed.

I passed on Sue Mosher's suggestion to disable any anti-virus software
and the most I could get out of the user was that "after doing that,
the problem went away about that time". I emailed him to see what
exactly he had running and never heard back. If I get a handle on
which specific script blocking software was running I will post to the
group.

Thanks everyone for the help (especially Sue!)
-mhd

 

[Ken Slovak - [MVP - Outlook]]

Early binding is not a problem even if supporting everything from Outlook
2000 to Outlook 2003. Just develop on a machine with Outlook 2000 installed.
Don't use any early bound methods that aren't there in Outlook 2000 (or
events or properties). If you want to use something that was introduced in
Outlook 2003 late bind that for that specific code segment:

Sub OnlyForOutlook2003()
Dim objOL As Object

Set objOL = g_objOL 'global early bound Outlook object