If you positively know that CDO is installed of course you don't need to
check for it being installed.

The old InstallFeature trick worked as long as the user was working with
Office 2003 or earlier because the CDO.DLL library was on the Office CDs.
With Office 2007 CDO is no longer on the CDs but instead has to be
downloaded from the MS Web site.

CDO is being deprecated, it most likely will not be supported in the next
version of Office (Office 14). That's just a guess, but if they come out
with native 64-bit versions of Office as now planned then no 32-bit addin
will work with 64-bit versions of Office and the old 32-bit CDO won't work.
Since CDO hasn't been developed in years other than security changes and
signature changes for new Outlook versions I seriously doubt that a 64-bit
CDO will ever be produced.

Now is the time to start moving code away from CDO to alternatives, if you
haven't already begun doing so.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"goran" wrote in message
...
Hi Ken,

Sorry to use this old thread, but this is the best way to get to you. I
use
your add-in wrapper to develop Outlook 2003 add-in with VB 6. It looks OK.
Now I want to use this add-in with Outlook 2007 and I have a problem when
it
tries to installFeature(CDO). I installed CDO manually myself. Do I need
to
check for CDO if I know that machine has it installed because I installed
it
manually?

Thanks,

Goran