Yes, that's what makes this different than the more common problem of the
program staying in memory after being closed. In this case, Outlook is open
(and behaving normally by all outward respects), but some condition is
causing a propogation of outlook.exe instances to the process list. And it
is the multiple instances that cause Send Mail commands in other apps to
fail.



Rick A.



"Diane Poremsky [MVP]" wrote in message
...
do you keep outlook open when the computer is running? I've never had a
problem with acrobat and others opening new instances as long as outlook
was running. When I close outlook, if something is keeping it open I can
end up with a lot of instances when I reopen it.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"Rick Altman" wrote in message
...
Thanks, Diane --

I am aware of the issue with apps that prevent Outlook from closing and I
am familiar with the small apps discussed at the link you gave. I am not
trying to close Outlook; I just want to prevent multiple instances from
starting. I did not initially think that my problem was related, but
perhaps it is. What do you think?


Rick A.





"Diane Poremsky [MVP]" wrote in message
...
It could be either.
http://slipstick.com/problems/close.asp

--