Labels, Option Buttons, and Multipage Controls

• Labels bound to flagged status A label bound to the flagged status of the message displays the correct status in OWA, but this differs from the behavior you may be accustomed to in Microsoft Outlook.
• Multiple option buttons When you design a form that includes option buttons, be sure to have only one of them selected (by binding to a value) as a default. Otherwise, more than one may be selected in the default state in your converted form, depending on the browser being used.
• Binding labels Binding a label to a property causes the value of that property to show up as the caption of the label, even if there is no value. If there is no initial value, do not use the label's Caption property as a replacement for setting an initial value. Instead, it is better to use the true initial value functionality.
• Disabling multipage controls If you disable a multipage control in your source Microsoft Outlook form, the Form Converter will disable it in the HTML form it generates, but the Web functionality will differ from that of Microsoft Outlook. Microsoft Outlook renders the multipage control, and its contents (other controls) as disabled. The generated HTML form renders the multipage control as disabled, but any controls on the visible (default) page of the multipage control are still functional. You can post-edit the resulting HTML files to disable any remaining active controls.
• Nesting multipage controls If you place a multipage control within another multipage control, be sure to leave several pixels of space around the perimeter of the interior control.