I count at least 2 objects that you aren't releasing in your close down
code. You need to be very careful to not keep any Outlook derived objects or
the addin won't let Outlook close. Another key thing to do is to make sure
you handle every possible error with an error handler.
Your test code should also be testing for Inspectors.Count as well as
Explorers.Count.

Signature
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
> Hi All,
>
[quoted text clipped - 59 lines]
>
> jz
jz - 23 Feb 2006 04:16 GMT
Thank you Ken, you are right, but also I observed that the order of the
objects to be cleaned is also very important; if I did respect set to
nothing from small objects to container, then it won't close correctly.
Ken Slovak - [MVP - Outlook] - 23 Feb 2006 14:38 GMT
I always start with my collections and unwind them if they contain objects
before I release the collection:
For i = colWhatever.Count To 1 Step -1
colWhatever.Remove i
Next
Set colWhatever = Nothing

Signature
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
> Thank you Ken, you are right, but also I observed that the order of the
> objects to be cleaned is also very important; if I did respect set to
> nothing from small objects to container, then it won't close correctly.