Article ID: 290780
Article Last Modified on 2/26/2004
APPLIES TO
- Microsoft Outlook 2002 Standard Edition
This article was previously published under Q290780
SYMPTOMS
You create a Visual Basic for Applications project in Outlook, and copy the underlying VBAProject.otm file to other users' computers so they can use it. But after they start Outlook, the Application_Startup event doesn't fire, or other macro functionality does not work as expected.
CAUSE
When you start Outlook, the Visual Basic for Applications component is not activated unless you've previously activated one of the Macro commands on the Tools menu.
RESOLUTION
After distributing the VBAProject.otm file, you must press ALT+F8 to activate the Macros windows, or press ALT+F11 to activate the Visual Basic Editor. You can then close either window, restart Outlook, and then the code will function correctly.
STATUS
This is a limitation of Outlook Visual Basic for Applications and there are no plans to change this behavior.
MORE INFORMATION
Visual Basic for Applications projects in Outlook are not designed to be distributable to large numbers of users. If you need to distribute an Outlook solution that uses application-level events and features of the Outlook object model, you should consider creating an Outlook COM Add-in.
For additional information about creating a COM add-in, click the article number below to view the article in the Microsoft Knowledge Base:
291163 OL2002: How to Create a COM Add-in for Outlook
REFERENCES
For additional information about working with the VBAProject.otm file, click the article number below to view the article in the Microsoft Knowledge Base:
290779 OL2002: Managing and Distributing Outlook VBA Projects
For additional information about available resources and answersto commonly asked questions about Microsoft Outlook solutions, click the article number below to view the article in the Microsoft Knowledge Base:
287530 OL2002: Questions About Custom Forms and Outlook Solutions
Additional query words: OutSol OutSol2002
Keywords: kbbug kbnofix KB290780
