Article ID: 2265542 - Last Review: March 8, 2012 - Revision: 5.0

Known issues in Outlook 2010 when you use Outlook 97-2003 custom forms

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SUMMARY

This article provides an overview of known issues in Microsoft Outlook 2010 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 Microsoft Office Outlook 2007 and in Outlook 2010.
Back to the top

MORE INFORMATION

The following sections in this article contain information about issues that 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 could 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:
  1. Click File, and then click Options.
  2. In the list of categories, click Trust Center, and then click Trust Center Settings.
  3. In the Trust Center, click the E-mail Security category.
  4. Click to enable Allow script in Public Folders.
For more information about how to change this setting by using policy settings, visit the following Microsoft TechNet website:
TechNet: Group Policy overview for Office 2010 (http://technet.microsoft.com/en-us/library/cc179176.aspx)


Path to public folders changed in Outlook 2010

In Outlook 2010, the top-level public folder name changed from Public Folders to Public Folders - username@org.com 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 needs 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:
Sub Item_Open()
   MsgBox GetTopLevelPublicFolderName
End Sub

Function GetTopLevelPublicFolderName()
   Set oSession = Application.GetNameSpace("MAPI")
   If Left(Application.Version,2) < 14 Then
      ' Set public folder for Outlook 2007 and lower
      GetTopLevelPublicFolderName = oSession.Folders("Public Folders")
   Else
      ' Set public folder for Outlook 2010 and higher
      strUserName = oSession.CurrentUser.AddressEntry.GetExchangeUser.PrimarySMTPAddress
      strFolderName = "Public Folders - " & strUserName
      GetTopLevelPublicFolderName = oSession.Folders(strFolderName)
   End If
End Function

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. One of the features of a custom action is the ability for the form to be sent immediately instead of opening a new form or prompting the user whether to send the form. If all the following conditions are true, Outlook does not send the form immediately, and the user is prompted to send the form:
  1. The form is a custom e-mail message form (message class of IPM.Note or a subclass of IPM.Note).
  2. The modified action is one of the built-in actions: Reply, Reply to All, Forward, or Reply to Folder.
  3. The user selects the action in the Outlook user interface (The Action.Execute method in the Outlook object model is not affected).

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 launch 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. Since online mode is de-emphasized, there are no plans to fix this problem.



Related Microsoft Knowledge Base articles

For the Outlook 2007 version of this article, click the following article number to view the article in the Microsoft Knowledge Base:
929591  (http://support.microsoft.com/kb/929593/ ) Known issues in Office Outlook 2007 when you use custom forms that were created by using earlier versions of Outlook
For 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
2265515  (http://support.microsoft.com/kb/2265542/ ) Known issues in Outlook 2010 when you use the object model
2265572  (http://support.microsoft.com/kb/2265572/ ) Known issues in Outlook 2010 when you try to develop form regions
2265568  (http://support.microsoft.com/kb/2265568/ ) Known issues in Outlook 2010 when you develop custom solutions
2511230  (http://support.microsoft.com/kb/2511230/ ) Known issues in Outlook 2010 when you use the Outlook View Control
Back to the top
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.
Back to the top
APPLIES TO
  • Microsoft Outlook 2010
Back to the top
Keywords: 
KB2265542
Back to the top