Are there any known ways to break Outlook COM such that 1 OUTLOOK.EXE
process will be running as a result of Outlook COM calls? I don't have
a few lines of code that can do this, but it seems to happen after a
Outlook COM call returns an error. After that, a new OUTLOOK.EXE will
appear. Once you have 1 OUTLOOK.EXE's running, the COM API becomes
somewhat unstable.

Jeff

Not handling all errors in a COM addin is an excellent way to leave Outlook
hanging. Since Outlook never closed properly any attempts to open a new
instance of Outlook will not be stable, and may even completely fail to
open.

Not releasing all your COM objects is another excellent way to prevent
Outlook from closing, and to prevent OnDisconnection from ever firing.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Jeff" wrote in message
ups.com...
Are there any known ways to break Outlook COM such that 1 OUTLOOK.EXE
process will be running as a result of Outlook COM calls? I don't have
a few lines of code that can do this, but it seems to happen after a
Outlook COM call returns an error. After that, a new OUTLOOK.EXE will
appear. Once you have 1 OUTLOOK.EXE's running, the COM API becomes
somewhat unstable.

Jeff