If you tried to call Inspector.Close() within Inspector.Send() that will
fire an exception. That's why I use the timer. It lets Send() finish and
then it fires and calls Close().

I've only had to use WM_CLOSE in cases of Simple MAPI Inspectors, which is
using a hack to close a hacked up window

The owner of the Outlook object model is well aware of all this sort of
thing. We'd discussed it for many years and I even had showed him how to
work with Simple MAPI Inspectors back when he was an Outlook MVP and we
worked on development projects together. No real resources have been spent
on Simple MAPI Inspectors in many years and I don't expect that to change.
We're lucky they are now added to the Inspectors collection, they weren't in
Outlook 2000 or before.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"SomewhereSomehow" wrote in
message ...
Thanks for the ideas, Ken!
Inspector.Close() - raises error, but posting WM_CLOSE to the window
work's
fine!
Nevetheless it seems to be not extremely brilliant solution because it
looks
like hiding the bug, but not fixing, but i guess we have no coise =)

But it works and that's greate!! Thank you once again for participating
and
clarifying the problem, I appreciate it much!

I'm now interested, is there any way to describe this bug and refer to
outlook developer team, so they can fix it in future versions or future
SP,
or am I very naive with this and nobody takes such misstakes into
consideration?..