OL2000: All COM Add-in Run-Time Errors Must Be Trapped

This article was previously published under Q208316
This article has been archived. It is offered "as is" and will no longer be updated.
You create an Outlook COM Add-in and when using it, Outlook stops responding (hangs).
The COM Add-in generated an untrapped run-time error.
You must use error trapping to prevent all potential run-time errors from happening.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
There are various scenarios where Outlook may hang if you create a COM Add-in and the code in the add-in generates an unexpected run-time error. This problem is related to how Office programs interface with the Visual Basic run-time, and is therefore a general limitation of the COM Add-in architecture.

To avoid these scenarios, every line of code within your COM Add-in must use error trapping to prevent any potential run-time errors from occurring.
For more information about how to implement error trapping in your code, please see the Microsoft Office 2000/Visual Basic Programmer's Guide, chapter 8, "Error Handling and Debugging."

For additional information about available resources and answersto commonly asked questions about Microsoft Outlook 2000 solutions,please see the following article in the Microsoft Knowledge Base:
146636 OL2000: Questions About Custom Forms and Outlook Solutions
OL2K OutSol OutSol2000 vbscript

Article ID: 208316 - Last Review: 10/11/2013 22:06:24 - Revision: 3.0

Microsoft Outlook 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbnofix kbprogramming KB208316