The information in this article applies to:
SYMPTOMSIn 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. CAUSEEvents 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. RESOLUTIONThis is a limitation of how Outlook implements the events. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products 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. REFERENCESFor additional information about available resources and answers to commonly asked questions about Outlook solutions, click the article number below to view the article in the Microsoft Knowledge Base: Q146636 OL2000: Questions About Custom Forms and Outlook Solutions Additional query words: OutSol OutSol2000 vba COM add-in start stop monitor
Keywords : |
Last Reviewed: January 4, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |