Article ID: 2265542 - View products that this article applies to.
This article describes the known issues in Microsoft Office Outlook 2010 that can occur when you use Outlook 97-2003 custom forms. The scope of this article is limited to custom forms that you create by using the method with which you would typically publish a form in these earlier versions of Microsoft Outlook. This article does not discuss custom forms that you create by using the form region feature in Outlook 2007 and in Outlook 2010.
The following sections in this article contain information about issues that can occur with custom forms in Outlook 2010.
By default, VBScript code does not run in public folders
By default, earlier versions of Outlook ran VBScript code in custom forms and scripts in folder home pages that were in public folders. This can be disabled by a policy setting or through the Outlook user interface. For more information about these settings, click the following article number to view the article in the Microsoft Knowledge Base: 838871
(http://support.microsoft.com/kb/838871/ )Description of the developer-related security changes in Outlook 2002 Service Pack 3 (SP3) In Outlook 2010, the default behavior was changed to prevent scripts from running in public folders. To re-enable this behavior in Outlook, follow these steps:
Path of public folders changed in Outlook 2010
In Outlook 2010, the top-level public folder name changed from Public Folders to Public Folders - firstname.lastname@example.org to support multiple public folder stores being available in a single MAPI profile. Custom form code that refers to the top-level folder as Public Folders has to be updated so that the correct folder name is used with Outlook 2010. The following VBScript code sample shows how to dynamically return the correct folder name based on which version of Outlook is being used:
Custom form action to send this form immediately is disabled
Outlook custom forms let form developer create custom actions that work like Reply, Forward, and so on. With a custom action, a form can be sent immediately instead of opening a new form, or users can be prompted to confirm that they want to send a form. If all the following conditions are true, Outlook does not send the form immediately, and the user is prompted to send the form:
This was a design change in Outlook 2010.
Publishing form in online mode may result in blank body
If you use a custom message form and the form's actions are set to open a custom form on reply, reply all, or forward, then the message body will be blank after the reply or forward is sent. This only happens if the form is published in Outlook online mode. As a workaround, publish the form while Outlook is in cached mode. Because online mode is de-emphasized, there are no plans to fix this problem.
Related Microsoft Knowledge Base articlesFor Outlook 2007, click the following article number to view the article in the Microsoft Knowledge Base:
929591For similar articles that cover issues with other aspects of the Outlook 2010 development platform, click the following article numbers to view the articles in the Microsoft Knowledge Base
(http://support.microsoft.com/kb/929593/ )Known issues in Outlook 2007 when you use Outlook 97-2003 custom forms
(http://support.microsoft.com/kb/2265542/ )Known issues in Outlook 2010 when you use the object model
(http://support.microsoft.com/kb/2265572/ )Known issues in Outlook 2010 when you try to develop form regions
(http://support.microsoft.com/kb/2265568/ )Known issues in Outlook 2010 when you develop custom solutions
(http://support.microsoft.com/kb/2511230/ )Known issues in Outlook 2010 when you use the Outlook View Control