Outlook email call from Access Runtime 2003

[Rick in NS]

I have posted this question to the automation board without any response and
hope someone in this discussion group will be able to help.

I am attempting to package a runtime version of an Access 2002 application
which includes vb code using SendObject to generate an email to Outlook.
When deploying the program on a PC that does not contain any version of
Outlook I understand I will have to deploy a file to the target machine which
the vb code will utilize to create an instance of Outlook. I have therfore
included the file MSOUTL.DLL in the package. However; when the code runs the
I get the error "Run-time error '429': Active X component can't create
object". A check of the file structure after installing the runtime
application shows MSOUTL.DLL in the Microsoft Office2003 directory but Access
cannot seem to find it. Any ideas on correcting this problem?

Does there have to be a registry entry made to somewhere to point to the
MSOUTL.DLL?

 

[Sue Mosher [MVP-Outlook]]

No file needs to be deployed. Outlook must be installed on the target machine. If it is and you continue to get that error, check whether your anti-virus tool has an active script blocker feature.

 

[Ken Slovak - [MVP - Outlook]]

First of all it's not legal to deploy any of the Outlook dll's or exe files.
Second, that's not enough to get an Outlook session, the user would have to
fully install Outlook from a legal copy of Outlook or Office.

Third, that SendObject command will call Outlook Express or other MAPI
provider if they are installed (Eudora is another MAPI provider) but it
doesn't use Outlook's Extended MAPI, SendObject uses Simple MAPI. If there
is a MAPI provider that Simple MAPI will call that instead of Outlook.

 

[Rick in NS]

I'm confused. In an online article at granite.abl.ca on "Late Binding in
Microsoft Access" it states: "Late binding means you do not have to concern
yourself with what version of other software, such as Word, Excel or Outlook,
being installed on the target system. Or if that software is not installed
at all on the target system."

Does not the fact the application was developed on Microsoft Office XP
Professional Developers edition and packaged with Visual Studio Developer
Extensions not give the license to distribute a run-time application to end
users with the ability to generate e-mails from Access VB code by calling an
instance of Outlook?

Appreciate you input.

 

[Ken Slovak - [MVP - Outlook]]

There is no license to deploy any Outlook components at all with VS, just
the ability to create Outlook compatible code. However, Outlook has to be
installed for the code to work.

Late binding lets you work with different versions of Outlook and to call
methods or properties not exposed in the version you have referenced. It
will never allow Outlook object model code to run if Outlook isn't
installed. If the article you saw says that then it's just flat out wrong.