Features Not Converted

Microsoft® Outlook™ offers a richer environment for the creation and use of forms than HTML does. Because of this inequality, certain features supported by Outlook forms cannot be converted to HTML.

You can work around this discrepancy in some cases. Sometimes you can start with a different feature in your original Outlook form to provide similar functionality. In other cases you may need to add the feature after form conversion, if possible, by editing the appropriate ASP file.

When designing your Microsoft Outlook form, pay particular attention to the following areas:

• Formulas The Form Converter does not convert formulas, though it does reproduce the formula verbatim in comment blocks to make post-editing of the form easier. The Form Converter does support initial values, type checking and formatting, and required fields.
• Script code Just as with formulas associated with a control, script code (whether or not it is associated with a command button) is not converted. Instead, the Form Converter generates a file called script.txt that contains all the code present in the original unconverted form, and saves this file into the folder that holds the generated form’s files. The To-Do list informs you that this has happened.
• Command buttons Because formulas and script code are not converted, neither are command buttons, which depend on script code for their functionality. Their layout is reproduced, but they are not functional in the converted form.
• Attachments If the source Microsoft Outlook custom form you want to convert has an attachment, the attachment will not be converted by the Form Converter.
• Stock pages The Form Converter converts a form's stock page only if you have modified that page in Microsoft Outlook. Otherwise, the standard stock page is copied unchanged from the subfolder it was placed in when the Form Converter was installed. However, changing a stock page causes the To: and Cc: Labels to show up as buttons instead of labels.

  Because these buttons do not function, the following errors (which appear in ToDo.txt) are generated during the conversion process:

  ToButton_3e_0_g: Button is associated with a recipient field, this association did not convert.
  CCButton_40_0_g: Button is associated with a recipient field, this association did not convert.

Note  You can identify a stock page by its name; examples are Stock_Details.asp and Stock_Address.asp.

For information on whether a given control is converted, see Working with Controls.