Packaging for multiple office versions

[John]

Hi

I need to package one of my access apps and send to clients. My app calls
outlook to send emails. The problem is that client pcs can each have a
different version of outlook (2000, xp, 2003 etc.). How can I package my app
that it will work with any version of outlook?

Thanks

Regards

[Sean]

If you package in 2000 then 2003 will be able to read it

[Danny J. Lesandrini]

What you want is Late Binding.

Rather than set a reference to Outlook (which is linked to a specific version),
you would do something like this ...

Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

The problem is that you don't get intellisense when you do this, so I usually
write my code with bound objects, using a specific reference, and then unbind
them before delivery ... or whenever I'm done working with the objects.

--
Danny J. Lesandrini
dl*********@hot mail.com
http://amazecreations.com/datafast

"John" <Jo**@nospam.in fovis.co.uk> wrote ...

Hi

I need to package one of my access apps and send to clients. My app calls outlook to send emails. The problem is that
client pcs can each have a different version of outlook (2000, xp, 2003 etc.). How can I package my app that it will
work with any version of outlook?

[Rick Brandt]

John wrote:

Hi

I need to package one of my access apps and send to clients. My app
calls outlook to send emails. The problem is that client pcs can each
have a different version of outlook (2000, xp, 2003 etc.). How can I
package my app that it will work with any version of outlook?

Late binding. This allows you to make use of external libraries without
setitng a reference to them and (for the most part) makes the code version
independent.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[John]

I am using

Private WithEvents objOutlook As Outlook.Applica tion

and if I change it to

Private WithEvents objOutlook As Object,

I get the error Compile Error, Expected: Identifier on the word Object. Any
way to fix this?

Thanks

Regards
"Danny J. Lesandrini" <dl*********@ho tmail.com> wrote in message
news:mN******** *************** *******@giganew s.com...

What you want is Late Binding.

Rather than set a reference to Outlook (which is linked to a specific
version),
you would do something like this ...

Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

The problem is that you don't get intellisense when you do this, so I
usually
write my code with bound objects, using a specific reference, and then
unbind
them before delivery ... or whenever I'm done working with the objects.

--
Danny J. Lesandrini
dl*********@hot mail.com
http://amazecreations.com/datafast

"John" <Jo**@nospam.in fovis.co.uk> wrote ...

Hi

I need to package one of my access apps and send to clients. My app calls
outlook to send emails. The problem is that client pcs can each have a
different version of outlook (2000, xp, 2003 etc.). How can I package my
app that it will work with any version of outlook?

[Douglas J. Steele]

Unfortunately, I don't believe you can use Late Binding in conjunction with
WithEvents.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"John" <Jo**@nospam.in fovis.co.uk> wrote in message
news:OO******** ******@TK2MSFTN GP15.phx.gbl...

I am using

Private WithEvents objOutlook As Outlook.Applica tion

and if I change it to

Private WithEvents objOutlook As Object,

I get the error Compile Error, Expected: Identifier on the word Object.
Any way to fix this?

Thanks

Regards
"Danny J. Lesandrini" <dl*********@ho tmail.com> wrote in message
news:mN******** *************** *******@giganew s.com...

What you want is Late Binding.

Rather than set a reference to Outlook (which is linked to a specific
version),
you would do something like this ...

Dim objOutlook As Object
Set objOutlook = CreateObject("O utlook.Applicat ion")

The problem is that you don't get intellisense when you do this, so I
usually
write my code with bound objects, using a specific reference, and then
unbind
them before delivery ... or whenever I'm done working with the objects.

--
Danny J. Lesandrini
dl*********@hot mail.com
http://amazecreations.com/datafast

"John" <Jo**@nospam.in fovis.co.uk> wrote ...

Hi

I need to package one of my access apps and send to clients. My app
calls outlook to send emails. The problem is that client pcs can each
have a different version of outlook (2000, xp, 2003 etc.). How can I
package my app that it will work with any version of outlook?

[Lyle Fairfield]

I have no interest in changing or criticizing anyone's practice of
automating Outlook in order to send e-mails.

I used to do this myself. I wrote my first code to do so about eight
years ago. Not so surprisingly there was a discussion then about early
and late binding.

I note there are many posts to CDMA outlining problems with automating
Outlook. I had problems myself, notably when system administrators
enetered fake addresses into system address books in order to confuse
the Melissa virus. They were successfull and they were also successful
in disabling an address search in my application. As they didn't tell
anyone, let alone me, of their covert activity, I was at a loss to
explain why the application worked one day, but not the next. [My first
rule of Access is: It's IT ('s fault).]

For beginners or non-previous-email senders who lurk I would like to
point out that beginning with Windows 2000, Microsoft has provided us
with CDO. CDO is implemented through CDOSys.Dll. CDO sends mail
quietly, simply, quickly, without warning messages and without fuss. I
use CDO now, I don't use Outlook.

[John]

Hi Lyle

Many thanks for that. Is it possible to post some sample code?

Many Thanks

Regards

"Lyle Fairfield" <ly***********@ aim.com> wrote in message
news:11******** **************@ g43g2000cwa.goo glegroups.com.. .

I have no interest in changing or criticizing anyone's practice of
automating Outlook in order to send e-mails.

I used to do this myself. I wrote my first code to do so about eight
years ago. Not so surprisingly there was a discussion then about early
and late binding.

I note there are many posts to CDMA outlining problems with automating
Outlook. I had problems myself, notably when system administrators
enetered fake addresses into system address books in order to confuse
the Melissa virus. They were successfull and they were also successful
in disabling an address search in my application. As they didn't tell
anyone, let alone me, of their covert activity, I was at a loss to
explain why the application worked one day, but not the next. [My first
rule of Access is: It's IT ('s fault).]

For beginners or non-previous-email senders who lurk I would like to
point out that beginning with Windows 2000, Microsoft has provided us
with CDO. CDO is implemented through CDOSys.Dll. CDO sends mail
quietly, simply, quickly, without warning messages and without fuss. I
use CDO now, I don't use Outlook.

[Lyle Fairfield]

http://groups.google.ca/group/comp.d...d9ac8179e2ba41

[TC]

More's the &^%$#$!@ pity.

Some of the SMTP mail components have terrific functionality, but also
use WithEvents. Since my own rule is "no early binding", I can't use
any of those components.

TC