Although restrictions were put on the control when it is used in a browser, the core functionality has stayed the same since 2001. For more information about the changes that were made in 2001, click the following article number to view the article in the Microsoft Knowledge Base:
Outlook shutdown and instancing issues
In earlier versions of Outlook, instances of the view control would keep the Outlook process running. However, changes to Outlook shutdown behavior can adversely affect the view control. When a user exits Outlook 2010, Outlook now shuts down completely. In this scenario, the view control becomes nonfunctional because Outlook is no longer running. For more information about architectural changes that are related to how Outlook shuts down, visit the following Microsoft Developer Network (MSDN) website:
Some problems that are related to the Outlook process may be avoided if Outlook is forced to start from an external program before the view control is rendered for the user. For example, you could automate Outlook and display an Outlook Explorer window to open Outlook before the view control is displayed or before a user interacts with the view control. However, because there are many variables and potential problems that are involved in scenarios such as these, we do not recommend this approach. Instead, we recommend that the view control is used only within Outlook. If you use the view control in any out-of-process scenario, Microsoft Customer Support cannot provide assistance, and hotfixes are not provided for these scenarios.
BUG #: 29202 (OfficeQFE)
The mouse does not work in Calendar view
If you set both the Folder and View properties to Calendar to display the Calendar view, the mouse does not function as expected. A fix for this issue is available in the Outlook 2010 hotfix package that is dated April 26, 2011. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
BUG #: 28154 (OfficeQFE)
SenderName and SentOnBehalfOfName properties no longer work with Outlook View Control Restriction
Both the SenderName and SentOnBehalfOfName properties refer to the From field in Outlook. If you use the Outlook View Control and either the SenderName or the SentOnBehalfOfName property together with the Restriction property, you receive an exception. The workaround is to use the Filter properties to search for items that are based on the From field. For example, you can use the following approach by using a Microsoft Visual Basic Scripting Edition (VBScript) script.
ViewCtl1.Filter = """urn:schemas:httpmail:fromname""" & " = 'John Smith'"
View control causes a rendering issue when the parent container is resized
If you use the view control on a custom form or on a webpage in a browser, and the parent window is resized, the view control may prevent the parent window from re-drawing the screen correctly. This symptom has the same cause as the mouse that does not work in Calendar view, and the resolution is the same.
Keyboard shortcuts do not work in Calendar view
You cannot use the keyboard in Calendar view. We are investigating this issue and will update this article with more information as it becomes available. If you must have a fix for this issue, please contact Microsoft Customer Support.
BUG #: 840972 (Office14)
Selection object does not return items in Conversation view
If a view is set to Show as conversations, the Selection object of the Outlook View Control does not return selected items. This problem was corrected in the Outlook 2010 Cumulative Update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Folder paths may have to be updated after an upgrade to Outlook 2010
If you are using the view control to display a public folder, the folder path is no longer valid after you upgrade to Outlook 2010. The top-level folder for public folders was changed from "Public Folders" to "Public folders - <username>." This change was made to support having more than one public folder store that is loaded in a single MAPI profile. To update solutions so that they can work with Outlook 2010, you can retrieve the Session.CurrentUser object to build the path that has the user's name.
Note This is another scenario where, if you use the view control in a browser, this workaround becomes more difficult, and even unrealistic. This is because, typically, you cannot automate Outlook directly from a browser to retrieve the current user's display name.
View names may have to be updated after an upgrade to Outlook 2010
Some view names have changed in Outlook 2010. For example, what used to be called Day/Week/Month view is now called Calendar view in Outlook 2010. Make sure that your solution uses the correct view names in Outlook 2010.
ID d'article : 2511230 - Dernière mise à jour : 26 août 2011 - Révision : 1