Python and CDO

[dsavitsk]

I may have my MS acronyms confused, but isn't CDO simply a COM object for
interfacing w/ Exchange?  COM allows Python to access and manipulate
Microsoft products, as well as everyone elses.  If CDOs do this too it would
seem redundant.  For a few simple writeups of Python and COM, see
http://www.e-coli.net/pyado.html and
http://starship.python.net/crew/bwilk/access.html. These are both database
COM objects.

I also have articles on the MS Word object, and COM client and server
development in python in the works, and I may post them someday too. Also,
look at the Python Cookbook
(http://aspn.activestate.com/ASPN/Python/Cookbook/) for many examples.

-d



"Lindstrom Greg - glinds" <Greg.Lindstrom at acxiom.com> wrote in message
news:mailman.1029426877.23369.python-list at python.org...
> Hi, all-
>
> I have been working with Python and Microsoft Collaboration Data Objects
> (CDO).  Simply put, CDOs allows Python to access and manipulate Microsoft
> products (Exchange, Word, Access, Excel, etc.) directly. [The book
> "Programming Python on Win32 has been an invaluable resource].  This has
> opened a world of possibilities where I work -- like it or not, Microsoft
> still owns the business desktop -- and though I have spent less than a
week
> looking into this, I already have had people stop by to ask if I could
look
> into their project.  And for the first time, Python is being talked about
as
> a legitimate tool for our group to use!  Very cool, indeed.
>
> I am going to start to research into all that CDOs have to offer, and
start
> writing tutorials for the various products.  Being pragmatic (and lazy), I
> do not want to duplicate any efforts which have been completed or are
> ongoing. So...are any of you using CDOs or looking into using them?  If
so,
> would you please get in touch with me?  If not, I will start writing and
see
> if the next edition of the Python Cookbook would be interested in a
section
> on this.
>
> Thanks for your time!
> --greg
> glinds at acxiom.com
>
>
> *********************************************************************
>
> The information contained in this communication is
> confidential, is intended only for the use of the recipient
> named above, and may be legally privileged.
> If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination,
> distribution, or copying of this communication is strictly
> prohibited.
> If you have received this communication in error,
> please re-send this communication to the sender and
> delete the original message or any copy of it from your
> computer system. Thank You.
>
>