I don't know why we see a lot of customers trying to automate Outlook from a service. It’s pretty well documented that it’s a bad idea. Outlook Object Model (OOM) was written for automating Outlook for a user sitting at the box running it. See, Outlook is very personal and I do mean, it’s very, very...

When you use OOM under .NET, your using managed code around COM objects via the Outlook Primary Interop Assembly (PIA). When you have managed code working with COM in this way, you have to be very careful to clean-up your references. .NET will hold onto COM objects, sometimes causing leaks, and sometimes...

How to display a message in an outlook window using the store id and item id using OOM. CDO 1.21 cannot just display a message without having it being in a state of forward, reply, etc - so OOM is a better solution. 'TODO - set a reference to the outlook object model ' Call DisplayMessage, passing...

Outlook Object Model (OOM) can do this easily. Below is a sample: howto - save and load a message to a folder. Sub SaveAndLoadMsgFile() Dim ol As Outlook.Application Dim olns As Outlook.NameSpace Dim oOrigItem As Outlook.MailItem Dim oNewItem As Outlook.MailItem Set ol = CreateObject("Outlook.Application...