[AccessD] Outlook Object Broken

You ARE referencing a specific Outlook object model, because ,as you
said, you have the made the reference:
<In my version the reference is to the Microsoft Outlook 9.0 Object
Library.  They recently upgraded to A2003 and their reference is now to
the Microsoft Outlook 11.0 Object Library.>
In order to have your application be version agnostic, take out your
reference to Outlook  ... Don't have any Outlook references, then
compile.  Your code must be moved completely to "late-bound" objects as
well: Dim objOutlook As Object
Set objOutlook = CreateObject("Outlook.Application"); dim objOutlookMsg
as Object, Set objOutlookMsg = objOutlook.CreateItem(0).

Hth
Steve



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
- Beach Access Software
Sent: Monday, June 28, 2004 5:21 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Outlook Object Broken


Doris:

I declare the object variables like this:

   Dim objOutlook As Outlook.Application
   Dim objOutlookMsg As Outlook.MailItem
   Dim objOutlookRecip As Outlook.Recipient
   Dim objOutlookAttach As Outlook.Attachment

Then it blows up on the very next line:

   ' Create the Outlook session.
   Set objOutlook = CreateObject("Outlook.Application")

So I'm not referencing the specific Outlook 9.0 library.  Is it possible
that they changed the names of the properties or methods or whatever you
call them in the Outlook 11 library - like changing .Application to .App
or some other humorous trick to keep us fully employed?

TIA

is

----- Original Message ----- 
From: "Mike & Doris Manning" <mikedorism at adelphia.net>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Monday, June 28, 2004 1:11 PM
Subject: RE: [AccessD] Outlook Object Broken


> We ran into a similar problem because we have many different operating

> systems in our organization.  We got around it by not referencing a 
> particular Outlook object model.
>
> Doris Manning
> Database Administrator
> Hargrove Inc.
> www.hargroveinc.com
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky 
> Smolin - Beach Access Software
> Sent: Monday, June 28, 2004 1:16 PM
> To: AccessD at databaseadvisors.com
> Subject: [AccessD] Outlook Object Broken
>
>
> Dear List:
>
> I provide an app to a client which uses the Outlook object to send 
> emails. In my version the reference is to the Microsoft Outlook 9.0 
> Object
Library.
> They recently upgraded to A2003 and their reference is now to the
Microsoft
> Outlook 11.0 Object Library.
>
> When my app hits the line of code:Set objOutlook =
> CreateObject("Outlook.Application")  it blows up saying it is unable 
> to create the object.
>
> Is there an easy fix or workaround to this problem?
>
> MTIA,
>
> Rocky Smolin
> Beach Access Software
> http://www.e-z-mrp.com
>
> --
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com