I apologize if this is not the correct discussion group to post this...I'm a
newbie.

Our software implements a Simple MAPI integration with Outlook (get Inbox
list and specific messages, create/send mail). I would like to change this,
but not sure what the best approach should be. Our customers use a variety
of Outlook versions (2000, 2003, 2007, Express).

I like the idea of an Add-in, but can't depend on the fact that Outlook is
running or that the customer even wants it to run. I'm not sure about CDO
since Outlook 2007 doesn't even install it anymore. I like the Automation
objects, but am not sure what to do with the security warnings pre-Outlook
2007. Would this be where Redemption comes into play? Any other suggestions?

Keep in mind that OE *only* supports Simple MAPI.
Outlook Object Model is the awy to go if you are targeting Outlook 2000 and
up.
See http://www.outlookcode.com/article.aspx?id=52 for the list of your
options regrading the security patch.

--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
-
"Jordan Hafer" <(E-Mail Removed)> wrote in message
news:92717678-44E6-42CB-BE38-(E-Mail Removed)...
>I apologize if this is not the correct discussion group to post this...I'm
>a
> newbie.
>
> Our software implements a Simple MAPI integration with Outlook (get Inbox
> list and specific messages, create/send mail). I would like to change
> this,
> but not sure what the best approach should be. Our customers use a
> variety
> of Outlook versions (2000, 2003, 2007, Express).
>
> I like the idea of an Add-in, but can't depend on the fact that Outlook is
> running or that the customer even wants it to run. I'm not sure about CDO
> since Outlook 2007 doesn't even install it anymore. I like the Automation
> objects, but am not sure what to do with the security warnings pre-Outlook
> 2007. Would this be where Redemption comes into play? Any other
> suggestions?