I use excel to control mailing of workbooks automatically using outlook. So
in my excel file I have the Outlook 11.0 reference file added in which is
associated with Outlook 2003, Unfortunately I have people using Outlook 2000
also which is using Outlook 9.0 reference library. When the excel workbook is
run a machine with outlook 2000 every macro errors because the reference to
the Outlook 11.0 library is not found. Is there a way to include backwards
compabtibilty here???????
Please help....
ben
--
When you lose your mind, you free your life.

"ben" (remove this if mailing direct) wrote in message
...
I use excel to control mailing of workbooks automatically using outlook.
So
in my excel file I have the Outlook 11.0 reference file added in which
is
associated with Outlook 2003, Unfortunately I have people using Outlook
2000
also which is using Outlook 9.0 reference library. When the excel workbook
is
run a machine with outlook 2000 every macro errors because the reference
to
the Outlook 11.0 library is not found. Is there a way to include backwards
compabtibilty here???????
Please help....
ben
--
When you lose your mind, you free your life.

I think so. When you have a reference set, you use what is known as early
binding, Thismeans that you can declare a varible to that object as Dim o As
Outlook.Application without VBA making a complaint. VBA can now make use of
Intellisense to show all the methods offered by Outlook.

I think you should be able to use late binding. This means that you remove
the reference to outlook and then have code similar to this

Dim o As Object
Set o = CreateObject("Outlook.Application")

You won't have Intellisense but the code should now work with either version
as long as you don't try to call a method that exists in one version only.
To make coding easier, do this change as the last step.

/Fredrik

You are referring to late binding, which doesn't bind to the application
type library at development/compile time, but makes multiple calls at
runtime.

Essentially, rather than setting a reference to the type library via
ToolsReferences, and then declaring an object of type Outlook.Application
or whatever, you create a generic Object variable and create that object
rather than just New.

You lose access to the application's object model and intellisens when you
do this, but there is another way, what I call Develop Early, Release Late.
An example is given (using Outlook) at
http://www.xldynamic.com/source/xld.EarlyLate.html

--

HTH

RP
(remove nothere from the email address if mailing direct)


"ben" (remove this if mailing direct) wrote in message
...
I use excel to control mailing of workbooks automatically using outlook.
So
in my excel file I have the Outlook 11.0 reference file added in which
is
associated with Outlook 2003, Unfortunately I have people using Outlook
2000
also which is using Outlook 9.0 reference library. When the excel workbook
is
run a machine with outlook 2000 every macro errors because the reference
to
the Outlook 11.0 library is not found. Is there a way to include backwards
compabtibilty here???????
Please help....
ben
--
When you lose your mind, you free your life.

"Bob Phillips" wrote in message
...
You are referring to late binding, which doesn't bind to the application
type library at development/compile time, but makes multiple calls at
runtime.

Essentially, rather than setting a reference to the type library via
ToolsReferences, and then declaring an object of type Outlook.Application
or whatever, you create a generic Object variable and create that object
rather than just New.

You lose access to the application's object model and intellisens when you
do this, but there is another way, what I call Develop Early, Release
Late.
An example is given (using Outlook) at
http://www.xldynamic.com/source/xld.EarlyLate.html

--


Develop Early, Release Late ? That sounds like something I want to
remember. Nice!

/Fredrik

thanks
I understood about late binding but i did not think about dim and setting
the objects differently
much appreciation.

"Bob Phillips" wrote:

You are referring to late binding, which doesn't bind to the application
type library at development/compile time, but makes multiple calls at
runtime.

Essentially, rather than setting a reference to the type library via
ToolsReferences, and then declaring an object of type Outlook.Application
or whatever, you create a generic Object variable and create that object
rather than just New.

You lose access to the application's object model and intellisens when you
do this, but there is another way, what I call Develop Early, Release Late.
An example is given (using Outlook) at
http://www.xldynamic.com/source/xld.EarlyLate.html

--

HTH

RP
(remove nothere from the email address if mailing direct)


"ben" (remove this if mailing direct) wrote in message
...
I use excel to control mailing of workbooks automatically using outlook.
So
in my excel file I have the Outlook 11.0 reference file added in which
is
associated with Outlook 2003, Unfortunately I have people using Outlook
2000
also which is using Outlook 9.0 reference library. When the excel workbook
is
run a machine with outlook 2000 every macro errors because the reference
to
the Outlook 11.0 library is not found. Is there a way to include backwards
compabtibilty here???????
Please help....
ben
--
When you lose your mind, you free your life.

"Fredrik Wahlgren" wrote in message
...

Develop Early, Release Late ? That sounds like something I want to
remember. Nice!

Thanks. I thought it was a good catchy phrase.

hmmm ok it compliles ok runs ok but it just doesn't mail
anything................

"Fredrik Wahlgren" wrote:


"Bob Phillips" wrote in message
...
You are referring to late binding, which doesn't bind to the application
type library at development/compile time, but makes multiple calls at
runtime.

Essentially, rather than setting a reference to the type library via
ToolsReferences, and then declaring an object of type Outlook.Application
or whatever, you create a generic Object variable and create that object
rather than just New.

You lose access to the application's object model and intellisens when you
do this, but there is another way, what I call Develop Early, Release
Late.
An example is given (using Outlook) at
http://www.xldynamic.com/source/xld.EarlyLate.html

--


Develop Early, Release Late ? That sounds like something I want to
remember. Nice!

/Fredrik

"ben" (remove this if mailing direct) wrote in message
...
hmmm ok it compliles ok runs ok but it just doesn't mail
anything................


Do you have an error handler in your code?

/Fredrik

nevermind, stupid me, the worst of all errors, syntax was incorrect for one
variable. sigh. I really need finish changing this project to option
explicit, thanks all

"ben" wrote:

hmmm ok it compliles ok runs ok but it just doesn't mail
anything................

"Fredrik Wahlgren" wrote:


"Bob Phillips" wrote in message
...
You are referring to late binding, which doesn't bind to the application
type library at development/compile time, but makes multiple calls at
runtime.

Essentially, rather than setting a reference to the type library via
ToolsReferences, and then declaring an object of type Outlook.Application
or whatever, you create a generic Object variable and create that object
rather than just New.

You lose access to the application's object model and intellisens when you
do this, but there is another way, what I call Develop Early, Release
Late.
An example is given (using Outlook) at
http://www.xldynamic.com/source/xld.EarlyLate.html

--


Develop Early, Release Late ? That sounds like something I want to
remember. Nice!

/Fredrik

You don't use Option Explicit all the time?

You know you can set that in ToolsOptionsEditor tab, Require Variable
Declaration checkbox.

--

HTH

RP
(remove nothere from the email address if mailing direct)


"ben" (remove this if mailing direct) wrote in message
...
nevermind, stupid me, the worst of all errors, syntax was incorrect for
one
variable. sigh. I really need finish changing this project to option
explicit, thanks all

"ben" wrote:

hmmm ok it compliles ok runs ok but it just doesn't mail
anything................

"Fredrik Wahlgren" wrote:


"Bob Phillips" wrote in message
...
You are referring to late binding, which doesn't bind to the
application
type library at development/compile time, but makes multiple calls
at
runtime.

Essentially, rather than setting a reference to the type library via
ToolsReferences, and then declaring an object of type
Outlook.Application
or whatever, you create a generic Object variable and create that
object
rather than just New.

You lose access to the application's object model and intellisens
when you
do this, but there is another way, what I call Develop Early,
Release
Late.
An example is given (using Outlook) at
http://www.xldynamic.com/source/xld.EarlyLate.html

--


Develop Early, Release Late ? That sounds like something I want to
remember. Nice!

/Fredrik