The fix I coded used a flag and a timer. I needed to do some work in
Inspector.Close but only after a few other things were done. So in Item.Send
I set a Boolean flag and at the top of Inspector.Close I test for that flag.
If True I just exit that event handler. A timer fires 500 ms after leaving
Item.Close and makes some procedure calls to do some things and then clears
the flag and explicitly closes the Inspector. Since the flag is clear the
cleanup code in Inspector.Close did it's work. This seems to have worked
around the bug.

--
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


"Ken Slovak - [MVP - Outlook]" wrote in message
...
That might vary depending on if Outlook 2000 was being used and also if an
Inspector wrapper class and collection are being used, which I use a lot.
And I have to support Outlook 2000. I was thinking of that or possibly a
flag set in Item.Send when canceling. That could be checked in
Inspector.Close as well as other procedures like timer events.