Troubleshooting forms
I can't find the form I created.
- The form may be visible only for message responses. To trigger the response form, create a form, such as a new message form, and then send it to yourself. Open the response form, click the (Properties) page, and then clear the Use form only for responses check box.
- The form may not have been saved, or it may not have been saved to a forms library.
- Based on the item type used, switching to a table view may make it easier to see the form.
My data is not being saved with the form.
Note If you drag a field from the Field Chooser, the control that is created will automatically be bound to the field.
The form is always saved with the item.
I can't change the default e-mail message form.
However, you can change the default mail message form that Microsoft Outlook will use in all folders. For more information, see Help.
New items aren't using my custom form.
Old items aren't using my custom form.
Received e-mail messages or post forms don't appear customized when read.
An incorrect version of a form is being used.
I can't find the message or notes property for an item.
I cannot open a password-protected form.
Remember that the password is case-sensitive.
If a form has been password-protected and the password is no longer known, Microsoft cannot help you circumvent the password protection.
Error: A field on this form requires a value.
Check whether controls on the form have field validation enabled in the Properties dialog box of the control.
If the error still appears, you must delete any unused custom fields that exist in the item, regardless of whether they appear on the form.
Use an Outlook Form in Microsoft Exchange.
The form commands are missing from the Tools menu, so I can't display the design environment.
- In the main Microsoft Outlook window, on the Tools menu, click Options, and then click the Mail Format tab.
- Clear the Use Microsoft Word to edit e-mail messages check box.
My solution doesn't run on other computers.
Use the following troubleshooting tips to help troubleshoot problems if your forms or programming solution works on some computers, but not others.
Microsoft Visual Basic Scripting Edition (VBScript) version If your solution involves forms that use VBScript, you may need to make sure that all computers are using the same version of VBScript that is being used on your development computer. VBScript is a shared component. Installing other software, such as a newer version of Microsoft Internet Explorer, may result in newer versions of VBScript being installed. For the latest information about VBScript versions, go to http://www.microsoft.com/scripting.
Controls If your solution uses any nonstandard controls, check to see if the controls are properly installed on all of the user's computers. If you are using any control other than one of the Forms 2.0 controls that are installed by Microsoft Office, you should provide your users with a Setup program to ensure that all of your controls are installed correctly.
Permissions or user rights Make sure that any user experiencing problems has proper permissions or rights to use any public folders or other resources that your solution uses.
Mail forms If your solution sends forms from one user's computer to another, did you select the Send form definition with item check box on the form's Properties page when in design mode? If not, you or the users must properly install the form so that it is available for users. Also, make sure that the computers are configured with the same type of mail accounts. Sometimes the type of message format (Microsoft Rich Text, HTML, or plain text) can play a role, as well as whether or not Microsoft Word is the e-mail editor. When the message is received, is the type of message format the same as when it was sent? Is it possible the format was converted during the send process?
VBScript code in the form does not run.
The macro virus warning keeps appearing.
If you published the form but still receive the warning message, this usually means one of two things: the Send form definition with item check box is selected on the form's Properties page; or the item has become a one-off form and the form definition, including VBScript code, has become part of the item itself.
The Click event of a control doesn't fire.