• Given certain Outlook Express' and Windows Mail's internal limitations, the best way to work is having the least amount possible of references to OEAPI objects.
  
  
• It is better to use one OEAPIObj using the objects' IDs (i.e. toolbars IDs, buttons IDs, menu items IDs, folders IDs, messages IDs, etc.).
  
  
• As soon as an OEToolbar, OEButton, OEFolder, etc. is no longer used, assign null/nothing to it.
  
  
• By this email client's limitations, it is better to have the least amount possible of references to OEFolder objects.
  
  
• On OnShutDownOEAPI() release every OEAPI object except OEAPIInit, and, at the end, call for the Garbage Collector twice:
  
  GC.Collect()
  GC.WaitForPendingFinalizers()
  GC.Collect()
  GC.WaitForPendingFinalizers()
  
  
• Do not call ReleaseComObject() for OEAPI objects, unless its imperative.
  
  
• If an object (i.e. inbox) is to be used frequently, it is better to have a reference to the object, than working with it's ID.
  
  
• If an object (i.e. toolbar) is to be used sporadically, it is better to obtain the object by it's ID using OEAPIObj.
  
  

 back