[AccessD] Outlook Automation Problem

Collins, Darryl Darryl.Collins at anz.com
Thu Jan 28 17:13:54 CST 2010


Hehehehe ""...the Programmer's Guild"

Where do I sign up?

Cheers
Darryl 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Friday, 29 January 2010 4:00 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Outlook Automation Problem


 "...the Programmer's Guild to maintain our cash flow..." Dang, they are
starting to figure it out.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, January 28, 2010 8:31 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Outlook Automation Problem

Ken:

Well, CDO is, I guess, an option if we can't figure out what's different
about this machine versus the other machines in that office. But I'd
have to figure out how to get it loaded onto his box, and change the
program - learning curve.  And the implementation would take some time
and this particular client doesn't want to spend any more money on his
app.  Which makes a lot of good solutions impractical. :)

I told him it's like a car.  You can drive your car a long way without
spending any money on maintenenance but eventually it breaks down.  I
think he suspects it's a plot by the Programmer's Guild to maintain our
cash flow.
:)

R

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth
Ismert
Sent: Thursday, January 28, 2010 8:09 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Outlook Automation Problem

Ken Ismert:
> Out of curiosity, are you using Outlook simply to send emails from 
> your application? Or, are you doing deeper integration with Outlook?

Rocky Smolin:
> In this case just making an email:

I've always found Outlook a pain to deal with if all you need to do is
send email. I just had a pleasant experience using CDO for Windows 2000
(CDOSYS), a component installed by default in Windows Windows 2000, XP,
and Server 2003. For Vista, Windows 7 and later, the library is
distributed as Collaboration Data Objects, version 1.2.1. (But, I
haven't tested 1.2.1)

Unlike the old CDO for NTS, I was able to easily send email with just
the address and port of a SMTP server using CDOSYS. The component
required no installation on my XP box.

Links:

About CDO for Windows 2000
http://msdn.microsoft.com/en-us/library/ms527525(EXCHG.10).aspx

Collaboration Data Objects for Windows 2000 (CDOSYS)
http://msdn.microsoft.com/en-us/library/aa142523.aspx

CDOSYS Examples (see ermora's snippet)
http://www.tek-tips.com/viewthread.cfm?qid=1280545

ASP Sending e-mail with CDOSYS
http://www.w3schools.com/asp/asp_send_email.asp

-Ken
--
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

"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential,  may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."




More information about the AccessD mailing list