Microsoft KB Archive/290802

= How to determine where to publish a custom Outlook form =

Article ID: 290802

Article Last Modified on 2/12/2007

-

APPLIES TO


 * Microsoft Outlook 2002 Standard Edition
 * Microsoft Office Outlook 2003

-



This article was previously published under Q290802







For a Microsoft Outlook 97 version of this article, see 264117.



For a Microsoft Outlook 98 version of this article, see 264118.



For a Microsoft Outlook 2000 version of this article, see 257796.



SUMMARY
This article describes some of the considerations to take into account if you are trying to decide where to publish a custom Outlook form.



MORE INFORMATION
In Outlook, custom forms are typically published to a forms library so that only one copy of a form is stored on your computer. Individual items contain a Message Class field that indicates which form to use to display the data that is contained in the item. When you publish custom forms to a forms library, Microsoft Exchange Server-based computers and Outlook use considerably less resources and bandwidth because the form itself does not need to be stored within each individual item.

Outlook forms solutions can vary greatly, especially because Outlook has a number of different types of standard forms. It is often difficult to determine the best place to publish a form, and there are many factors to take into account when you make the decision.

Where You Can Publish Forms
Forms can be published to three locations. The following table outlines those locations.

It is also possible to store an Outlook form as a file in the file system or as an item in an Outlook folder. Microsoft recommends that you avoid both of these approaches, however, because the form will be a one-off form. For additional information about one-off forms, click the article number below to view the article in the Microsoft Knowledge Base:

290657 OL2002: Working with Form Definitions and One-Off Forms

You can save an Outlook form to the file system as an Outlook Template (.oft) file. This allows you to attach the form to an e-mail message, and then send the form to someone else. You can also use the .oft file as a backup of the form. To save a form as an .oft file:
 * 1) On the File menu, click Save As.
 * 2) In the File name box, type a name for the form.
 * 3) In the Save as type box, click Outlook Template, and then click Save.

You can also save the form as an item in the current folder. However, Microsoft doesn not recommended that you do this for the following reasons:
 * It is easy to accidentally delete the form.
 * It tends to blur the distinction between forms and items, and the typical result is a folder that is filled with different items that contain various versions of the same form. This is generally not a good practice when you design Outlook forms.
 * Items that are stored in a folder typically have data associated with them, and you usually do not want data associated with your form. Therefore, Microsoft recommends that you not open an item in a folder and then enter design mode; open a new instance of the form and then enter design mode.
 * Forms that are stored as items are &quot;one-off&quot; forms and have unwanted side effects.

To save a form in the current folder, click Save on the File menu.

Considerations When You Are Deciding Where to Publish a Form
There are many questions to take into account when you are deciding where to publish a form:
 * Is the form based on a folder solution, or is it an e-mail message form that is designed to be sent to recipients?
 * Are you using an Exchange Server-based computer? If you are using an Exchange Server-based computer, is it possible to publish the form to the Organizational Forms Library, or has your organization placed restrictions on what types of forms can be stored there?
 * How many people need access to the form?
 * Will the form be updated often, making it important to have only one copy of the form deployed centrally?
 * Does the form need to be available offline?
 * If this is an e-mail message form, will it be used only inside the organization, or will it be sent to other recipients outside of the organization?
 * How will the new form be opened?

Deciding Where to Publish Folder-based Forms
When you create a folder-based solution where the primary focus of the form is to display the items in a single folder, typically publish the form to the folder itself. When you publish the form to the folder, the folder is a self-contained entity and the form is available on the Actions menu.

However, there are scenarios where you may not want to publish a typical folder-based form to a folder. If you use a form in more than one folder, and each folder always uses the same version of the form, consider publishing the form into either the Organizational Forms Library or the Personal Forms Library. When you do this, there is only one copy of the published form and it is easier to update if you need to make changes. If you are the only person who needs access to this form, publish the form in Personal Forms Library. If other people need to access to the form, and the form is typical in a public folder on an Exchange Server-based computer, investigate whether or not you may be able to publish the form to the Organizational Forms Library. One potential disadvantage to this approach is that the form will not be available under the Actions menu unless it is published to the folder. However, if it is the default form for the folder, as is typically the case, this will not make too much of a difference because you or the users can use a toolbar button to open new items.

Deciding Where to Publish Message-based Forms
If the form is based on an e-mail message and it is used by you and only a couple of other users, publish the form to the Personal Forms Library for all of the users. However, if you are going to create new items based on this form, you may want to publish it to your Inbox so that you can access it on the Actions menu. If the form is going to be used by many people within an organization, publish it in the Organizational Forms Library so that there is only one copy of the form to maintain and all of the users have access to it. This approach, however, can make the form more difficult to open.

Considerations and Options for Opening Forms
The following table describes how users typically open Outlook forms depending on where the forms are stored:

You can use the following methods to make forms more accessible to users.

Add the &quot;Choose Form&quot; Command to the Toolbar
To shorten the number of steps that are needed to access the Choose Form command, add the command to the toolbar so that you can display the dialog box with a single mouse click:
 * 1) On the View menu, point to Toolbars, and then click Customize.
 * 2) Click the Commands tab in the Customize dialog box.
 * 3) In the Categories box, make sure that File is selected.
 * 4) In the Commands box, locate the Choose Form command, and then drag it up to the toolbar location that you want.
 * 5) Click Close.

Open a Form by Using Visual Basic for Applications or a COM Add-in
For additional information about how to use Visual Basic for Applications to open a form from a toolbar or menu, click the article number below to view the article in the Microsoft Knowledge Base:

290803 OL2002: How to Open a Form from a Toolbar Button

Publish the Form to a Folder
If a form is published to either the Personal Forms Library or the Organizational Form Library, you may want to consider publishing a form to a folder so that it appears on the Actions menu. However, if the form is updated, be sure that the form is re-deployed so that you do not create problems with the Outlook forms cache. For additional information about the forms cache, click the following article numbers to view the articles in the Microsoft Knowledge Base:

290806 How the Forms Cache Works

Save an .oft File to the Desktop or Start Menu
Although Microsoft does not typically recommend saving an .oft file to the desktop or to the Start menu, you can save an Outlook Template (.oft) file to either location. The items that are created by doing this contain &quot;one-off&quot; forms that typically cause unwanted side effects depending on the design of the form and how it is used.

For additional information about one-off forms, click the article number below to view the article in the Microsoft Knowledge Base:

290657 OL2002: Working with Form Definitions and One-Off Forms

