E
Eric
I wrote a program which uses MAPI to dump email from another program
into the Outlook inbox. I also wrote another program which does about
the same thing, but via the Outlook Object Module (OOM). Both are
written in C and C++.
The one which uses the Outlook Object Module has less tech support
issues, and the one which uses MAPI always generates tech support
calls, usually because the MAPI dlls are mixmatch of versions, stubs,
etc. We would like to dump the MAPI version and go with just OOM, but
the OOM is limited.
Anyway, my question is about ADO. If we go with ADO I understand this
does not run over MAPI, great! But is it like the OOM which limits
which fields you can access? Mostly I'm just trying to access
standard fields, but one field which I can't access via OOM is the
"message flags" field, which I need to use to clear the "un-sent" flag
when dumping messages into the Outlook inbox.
I may end up using a combo of MAPI and OOM, but I would love to avoid
MAPI all together if possible.
into the Outlook inbox. I also wrote another program which does about
the same thing, but via the Outlook Object Module (OOM). Both are
written in C and C++.
The one which uses the Outlook Object Module has less tech support
issues, and the one which uses MAPI always generates tech support
calls, usually because the MAPI dlls are mixmatch of versions, stubs,
etc. We would like to dump the MAPI version and go with just OOM, but
the OOM is limited.
Anyway, my question is about ADO. If we go with ADO I understand this
does not run over MAPI, great! But is it like the OOM which limits
which fields you can access? Mostly I'm just trying to access
standard fields, but one field which I can't access via OOM is the
"message flags" field, which I need to use to clear the "un-sent" flag
when dumping messages into the Outlook inbox.
I may end up using a combo of MAPI and OOM, but I would love to avoid
MAPI all together if possible.