CDO 1.21 and Outlook Object Model

[Neil Dittmar]

Hello All,

I've begun playing around with CDO 1.21 in an effort
to allow a Visual Basic application to log into multiple
Exchange Server mailboxes. Using the Logon event of the
CDO Session Object, I'm logging into the mailbox I want to
access on Exchange and can successfully get to the various
items inside of it (Inbox, Calendar, etc.)
programatically. I'm wondering if there is a way to
display this information onscreen via Outlook (either
using CDO 1.21 alone, or in combination with the Outlook
Developers Object). I understand that I could design and
code forms in VB to allow the user to view/modify the
information retrieved using the CDO sessions, but I'd
rather let Outlook handle user interactions if possible.
Any suggestions?

Thanks,

Neil Dittmar
Software Developer
Aurora Information Systems

 

[David Kane]

Neil,

You can have CDO piggyback onto an existing Outlook session (by not supplying blanks paramters in Session.Logon) but you can't get Outlook to recognize or display anything from a CDO session. You can use Outlook's GetSharedDefaultFolder method to open folders in another user's mailbox (assuming that your account has permission). The Outlook object model (OOM) can be used to open a separate Explorer window to display the contents of that other user's folder.

----- Neil Dittmar wrote: -----

Hello All,

I've begun playing around with CDO 1.21 in an effort
to allow a Visual Basic application to log into multiple
Exchange Server mailboxes. Using the Logon event of the
CDO Session Object, I'm logging into the mailbox I want to
access on Exchange and can successfully get to the various
items inside of it (Inbox, Calendar, etc.)
programatically. I'm wondering if there is a way to
display this information onscreen via Outlook (either
using CDO 1.21 alone, or in combination with the Outlook
Developers Object). I understand that I could design and
code forms in VB to allow the user to view/modify the
information retrieved using the CDO sessions, but I'd
rather let Outlook handle user interactions if possible.
Any suggestions?

Thanks,

Neil Dittmar
Software Developer
Aurora Information Systems