I have no idea how that other link relates to this but just use GetObject()
to see if Outlook is running, if not use CreateObject().

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Old Man River" wrote in message
...
I am trying to run this subroutine from an Excel Macro in a Scheduled job.

Private Sub SendMessage()
Dim OutApp As Object
Dim OutMail As Object
'ToStr, Subject and strBody are globals in the Excel VB Module.

Set OutApp = CreateObject("Outlook.Application")
Set OutMail = OutApp.CreateItem(0)
With OutMail
.To = ToStr
.CC = "xxx@yyy" 'Real address obscured here.
.BCC = ""
.Subject = Subject
.Body = strbody
.Send
End With
End Sub

It works perfectly when triggered by opening the spreadsheet which has an
auto run macro which invokes the code. Either manually from Excel or by
running the Command Line "C:\Program Files\Microsoft
Office\Office12\Excel.exe" /r "C:\Users\Alan\Documents\HSC\Fence
Check\Fence
Check Auto Run.xlsm"

Normally the scheduled task that runs the same code (there is a bit more
to
it) runs perfectly but when it hits the above it is failing and as a
result
screwing up the scheduled job which then fails to complete and
subsequently
will not run until after a reboot and re-registering the task.

This is a follow on from a previous thread viz:
http://social.answers.microsoft.com/...?prof=required

Can anybody help or suggest a workaround. P.S. I always have Outlook Open
on
my Desktop and I hate having to late bind the Objects in this code.

---Also posted in Office Developer Automation - but seems a pretty
inactive
forum.