CDO vs. Outlook Object Model
For me it always depends on the task at hand. CDO is great because it
exposes objects/methods that are not present in the Outlook Object Model.
In your case, if you don't need to show any items to the user then cdo would
be the direction to go.
Quote:
> CDO (cdo.dll) vs. Outlook Object Model (msoutl9.olb)
> What direction should I code to? I have to integrate with Outlook
> specifically with a VB application. I will be doing some meeting, email,
and
> contact
> queries/imports. Is there reason to choose one over the other? CDO seems
to
> give more functionality.
> ~Bebo
