Using Command Files with HTML2 and HTML4 output in Release 7.2

Document ID : KB000055834
Last Modified Date : 14/02/2018
Show Technical Document Details


Release 7.2 reintroduces support for the HTML2 report output format. Previous releases supported only one HTML format: release 7.0 supported only HTML2, and release 7.1 supported only HTML4. HTML2 support is reinstated in release 7.2 for clients who had previously created reports designed for HTML2 output. So in Release 7.2, HTML2 and HTML4 formats are available. This tech doc will discuss how this affects command file users.

Operating Systems

Win2000, Win2003, AIX, HP, Solaris

A new setting, called HTML EXPORT_FMT Control, is found in the Report Viewer under Tools > Database Connection Defaults.

Figure 1

Users who created command files in versions prior to 7.1 might have specified uppercase H or lowercase h as the EXPORT_FMT for HTML output. Use the EXPORT_FMT Control to specify how the application should interpret the "H" or "h" specifying the EXPORT_FMT parameter in the command files.

Example Command File
Figure 2

When the HTML EXPORT_FMT Control check box is marked, an uppercase letter H in a command file is interpreted as HTML4, and a lowercase letter h is interpreted as HTML2. Conversely, when the HTML EXPORT_FMT Control check box is cleared, an uppercase letter H is interpreted as HTML2, and a lowercase letter h is interpreted as HTML4.

NOTE: The HTML EXPORT_FMT Control setting applies only to command file users. Users that have existing command files, consider the following items:

  1. Should reports continue to create HTML2 output or should they create new HTML4 output?
  2. In existing command files, is the EXPORT_FMT parameter specified with an upper- or lowercase letter H? For example, if HTML2 output is desired and existing command files use an uppercase letter H to indicate the EXPORT_FMT, you must clear the HTML EXPORT_FMT Control check box.

Related Documents

HTML2 and HTML4 output supported in Release 7.2


We take pride in our technical documents and are interested in your feedback. Please email your comments to us directly at:
Be sure to include the document id in the message.