>>>>>>>>>>>>>> Thanks. Unfortunately completely releasing the object in Send isn't a real
>>>>>>>>>>>>>> good solution in many cases.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> For one example, you do some item processing in Send and then have to start
>>>>>>>>>>>>>> up a timer object to allow closing the Inspector using code, something that
>>>>>>>>>>>>>> will cause an exception if you do it in the Send event. So you set a timer
>>>>>>>>>>>>>> for a short interval at the end of Send and when the timer fires you call
>>>>>>>>>>>>>> Inspector.Close().
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Calling Marshal.ReleaseComObject() on the item in Send would prevent that
>>>>>>>>>>>>>> code from working at all.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'll see if I can verify your bug here and if so I'll file it with the
>>>>>>>>>>>>>> product group. That way we can be sure that they're aware of it. A lot of
>>>>>>>>>>>>>> times if first line support files something it gets lost in the shuffle.
>>>>>>>>>>>>>> It's only if you get to the higher-ups on the support front that their bug
>>>>>>>>>>>>>> reports are paid attention to.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Why don't you email me a couple of your small samples please, use my posting
>>>>>>>>>>>>>> address, I'll get them. Then I can review them and see what's going on. If
>>>>>>>>>>>>>> you don't mind giving me the name of the PSS engineer you worked with and
>>>>>>>>>>>>>> the bug case # too, that would help when I get back to the product group.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Tim Pulley" <TimPulley@discussions.microsoft.com> wrote in message
>>>>>>>>>>>>>> news:60EE3228-4056-409B-B224-25D981234E10@microsoft.com...