That's CDO 1.21, which is completely different from the CDO for Windows library that I recommended as a way of bypassing Outlook completely. If you want to use CDO 1.21 and contend with its security prompts, you can use its Session.DeliverNow method to send whatever is in the Outbox.

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


"Robin9876" wrote in message ...
I have used the VBA example code for CDO message from the following
Microsoft KB article http://support.microsoft.com/kb/161833

However the message were queued up in in this profile until I logged
in to it in Outlook.

How is it possible in the code to force a send message for this
profile?

On 27 Nov, 17:34, "Sue Mosher [MVP-Outlook]"
wrote:
Nothing in particular happens. CDO for Windows doesn't use Outlook in any way.

"Robin9876" wrote in ...
Do you know what happens if you already have Outlook open on the pc
and then use CDO to send a message from another VBA application?

On 26 Nov, 17:13, Robin9876 wrote:
Yes it is IMAP, so the SMTP by sending either with the toolbar or CDO
should work.

On 23 Nov, 18:55, "Sue Mosher [MVP-Outlook]"
wrote:

Do you mean IMAP, not LMAP? IMAP is a protocol for receiving messages. SMTP is the protocol used for sending.

"Robin9876" wrote in ...
It is connecting to a mail server via LMAP which I thought CDO only
connects to SMTP server?

On 23 Nov, 15:48, "Sue Mosher [MVP-Outlook]"
wrote:
Not if Outlook is already running. Only one Outlook session can be running at a time.

Is Outlook really necessary to your Access application? Have you thought about using CDO for Windows to send directly through an SMTP server?