Newbie wants to connect using CDO instead of MAPI

[burkejay]

I have the following VBA code that uses MAPI to get a user's Appointments.
It generates the dreaded security access dialog, so i want to use CDO
instead, but I don't know how.

Dim ol As New Outlook.Application
Dim olns As Outlook.NameSpace
Dim recip As Outlook.Recipient
Dim rs As Recordset

Set olns = ol.GetNamespace("MAPI")

Set rs = CurrentDb.OpenRecordset("SELECT OUTLOOK_USERID FROM
USER_ACCOUNTS")
rs.OpenRecordset

Set recip = olns.CreateRecipient(rs!OUTLOOK_USERID)
recip.Resolve rem security prompt opens here.

How do I replace the CreateRecipient and resolve with CDO
objects instead?

Thanks!

 

[Sue Mosher [MVP-Outlook]]

Why? CDO 1.21 always raises security prompts.

Is this code for Outlook VBA? If so, this is your problem:

Dim ol As New Outlook.Application

Instead, use the intrinsic Application object that Outlook VBA exposes:

Set ol = Application

or just

Set olns = Application.GetNamespace(MAPI)

 

[Dmitry Streblechenko]

Firstly, you are using the Outlook Object Model, not MAPI (which is only
accessible in C++ or Delphi).
CDO 1.21 is crippled just like OOM. See
http://outlookcode.com/article.aspx?id=52 for the discussion.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[burkejay]

Sorry that I failed to mention it is in Access VBA.

I commented out the whole line "Dim ol As New Outlook.Application"
and just did a straight "Set olns = Outlook.Application.GetNamespace("MAPI")"

and I still got the security warning.

Thanks so much for your help!

 

[Ken Slovak - [MVP - Outlook]]

From outside the Outlook VBA, like in Access VBA, you would use New
Outlook.Application.

However, you aren't understanding that the project reference to MAPI is
actually CDO 1.21 and your MAPI.Session is a CDO Session object. CDO is
restricted and no matter what you do if you use it you will get the security
prompts.

I think you are confusing Extended MAPI with CDO (MAPI). Extended MAPI has a
huge learning curve and cannot be programmed using VBA, only C++ or Delphi
in unmanaged code.

 

[burkejay]

My mistake, I had skimmed that very discussion and that was where I got
the idea that I needed to use CDO. I must have misread it, sorry.

 

[Sue Mosher [MVP-Outlook]]

That's hugely relevant. External Outlook automation is going to raise security prompts in versions before Outlook 2007. See http://www.outlookcode.com/article.aspx?ID=52 for your options.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54