Article ID: 249155
Article Last Modified on 9/29/2003
APPLIES TO
- Microsoft Outlook 2000 Standard Edition
This article was previously published under Q249155
SYMPTOMS
In a custom solution, you implement the SyncStart, SyncStop, or Progress events for the SyncObject object, but the events do not fire when the code is run.
CAUSE
Events related to SyncObjects only fire if the synchronization is started programmatically. If the user initiates the synchronization using the Outlook user interface, the events do not fire.
RESOLUTION
This is a limitation of how Outlook implements the events.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
If you need to use these events when the user initiates the synchronization, replace the Outlook synchronization commands with your own custom menu commands that programmatically start the synchronization process.
IMPORTANT: In general, this will result in a somewhat complex solution and you will most likely lose some of the built-in Outlook functionality. In addition, the F9 key cannot be modified so users can still synchronize by pressing F9, bypassing your solution. In the end, this approach is not realistic in most cases.
REFERENCES
For additional information about available resources and answersto commonly asked questions about Outlook solutions, click the article number below to view the article in the Microsoft Knowledge Base:
146636 OL2000: Questions About Custom Forms and Outlook Solutions
Additional query words: OutSol OutSol2000 vba COM add-in start stop monitor
Keywords: kbbug kbprogramming KB249155
