Export Options

Use this window to specify options for exporting data from the Table or Summary window.

To access this window select Options from the Home ribbon, then select Export from the Options Window ribbon.

Export Field Names

Field

Description

Include field names as the first row of output

Use this setting to export the Table window field names (or Summary window column titles) when exporting data to a text file, a delimited text file or HTML formats.

Note: Field names are always exported to database formats, dBASE DBF format, and MS-Access MDB format and to spreadsheet formats (XLS) when exporting via the Jet database engine. They are also always exported to XLSX and XLS when using the Monarch Classic 10.5 Engine.

Repeat field names on each page (Applies to fixed-width text files with pagination enabled)

Exports the Table view field names (or Summary window column titles) to each page when exporting data to a fixed-width text file with pagination enabled.

Get column names for summary exports to database formats from:

When exporting a summary to a database, specify where you want to get the column names from -- i.e., from either the Table window field names or the Summary window column titles -- by selecting the appropriate option..

  • Field Names:  When exporting from a summary to a database, select this radio button if you want the field names in the table to dictate what the column names in the database will be.

  • Column Titles:  When exporting from a summary to a database, select this radio button if you want the column titles in the summary to dictate what the column names in the database will be.

 

Export Excel Files

Field

Description

Apply formatting to XLS and XLSX files

Use this setting to reflect Monarch Classic's formatting as far as possible when exporting to Excel. This creates only a very small performance impact.

Apply the Export Wizard’s "Advanced Excel Features."

Enables exports from the Summary using Excel Formulas, Excel Conditional Formatting Rules, and Outlining. It also enables the AutoFilter and Pivot Table options when exporting from the Table view.

 

Export Text Files

Field

Description

For Fixed-length Text Files options

Pad each field with one extra space

Use this setting to separate exported fields with an extra space when exporting to a text file or a delimited text file. With this option unselected, field values might "bump up" against each other producing, for example, "123.45CD" rather than "123.45 CD".

Pad numeric fields with zeros, suppress the decimal point, and use trailing negation

Use this setting to export numeric fields using a standardized format that pads each value with leading zeros, removes the decimal point and places the negation sign at the end of the field value. This format represents the number "-123.45" as "00012345-". When selected, this option reformats each numeric field whose type is set to "Numeric" (as opposed to Thousands, Currency, or Percentage), removing the decimal character, and then padding the field with sufficient leading and trailing zeros to match the field’s column format, preserving the rightmost character position for a trailing negation sign.

For Delimited Text Files options

Put "Quotes" around character field values

Use this setting to enclose character fields in quotes when exporting to a delimited text file.

Why Enclose Character Fields in Quotes? - A comma is the most common field delimiter used in delimited ASCII files. Since commas are often used in description fields, a field value such as "Brahms, Symphony No.1" might be interpreted as two consecutive field values - "Brahms" and "Symphony No.1". By enclosing character fields in quotes, the value would be correctly interpreted as a single field, "Brahms, Symphony No.1".

When a character field value includes a quote character, Monarch Classic appends a second quote character immediately following the original. This allows an application reading the delimited text file to interpret an individual quote character as designating the end of a string and a pair of quote characters as designating an individual quote character within a string.

Put "Quotes" around field names on the first row

This encloses the data on the first row of the file in quotes. As a rule, this data will be the field names. This option is provided to enable compatibility with systems that expect the data in this format.

Delimiter

Select the appropriate radio button to specify the character to use for separating field values when exporting to a Delimited Text file. Note: The most common delimiter character is a comma. When selecting the Other option, enter the desired character in the adjacent field.

Date format

Select the preferred format for exporting date values. Valid options are yyyy-mm-dd and yyyymmdd.

For both Fixed-length and Delimited Text Files options

Append DOS end-of-file character (x1A)

This option determines whether or not a DOS end-of-file character (x1A) is appended to the end of the file. This option is provided to enable compatibility with systems that expect the data in this format. This end-of-file character is often known as Control-z.

Encoding

Use this setting to specify the default export  format. The following encodings are supported by Monarch Classic:

  • ASCII: Select to make Monarch Classic interpret report files as ASCII text and perform the conversion to ANSI. This is the default setting because most report files are created as ASCII text files.

  • ANSI: Select to make Monarch Classic read report files as ANSI text and perform no conversion. While most report files are created as ASCII text files, report files generated from Windows applications may be created as ANSI text files. The difference lies with characters 128 - 255 in the character set: in these positions, the ANSI character set includes international characters not present in the ASCII character set.

  • UTF-8  (8-bit Unicode Transformation Format): Select to make Monarch Classic interpret report files as UTF-8 files. UTF-8 is a variable-length character encoding for Unicode, which is able to represent any character in the Unicode standard, yet it is backwards compatible with ASCII. If a valid BOM (Byte order mark) is detected within the input file, then Monarch Classic will automatically select the UTF-8 type when opening the file.

  • UTF-16 LE (16-bit Unicode Transformation format, Little Endian): Select to make Monarch Classic interpret report files as UTF-16 LE files. UTF-16 LE is the Unicode Transformation Format that serializes a Unicode value as a sequence of two bytes, in little-endian format. If a valid BOM (Byte order mark) is detected within the input file, then Monarch Classic will automatically select the UTF-16 LE type when opening the file.
    Note: "Little Endian" means that the low-order byte of the number is stored in memory at the lowest address, and the high-order byte at the highest address. This is a function of the processor architecture. Windows, VAX/VMS, Digital Unix, Mac (Intel) are examples of little-endian systems. MIPS systems can often be configured to be either little-endian or big-endian. Linux can also be configured to run on little and big-endian hardware.

  • UTF-16 BE (16-bit Unicode Transformation format, Big Endian): Select to make Monarch Classic interpret report files as UTF-16 BE files. UTF-16 BE is the Unicode Transformation Format that serializes a Unicode value as a sequence of two bytes, in big-endian format. If a valid BOM (Byte order mark) is detected within the input file, then Monarch Classic will automatically select the UTF-16 BE type when opening the file.
    Note: "Big Endian" means that the high-order byte of the number is stored in memory at the lowest address, and the low-order byte at the highest address. IBM mainframe, HP-UX, Solaris, the Java Virtual Machine and Mac (Motorola, PowerPC) are examples of big-endian systems.

Code page

Select the appropriate code page to use with the chosen input file encoding format. This option is only applicable to the ASCII (14 codepages available) and ANSI (10 codepages available) encoding systems.

ANSI Locale

Select the appropriate locale for ANSI Encoding. This drop-down is only active if your encoding is ANSI.

You can select to use:

  • Default

  • Western locale

  • Japanese locale

 

 

DB and DBF Files

Field

Description

DBF Files

Displays the file format and version to be used when exporting dBASE DBF files. The drop-down list includes all supported versions of the dBASE DBF file format.

MDB Files

Displays the file format and version to be used when exporting Access MDB  files.

 

Report View - File Naming

Field

Description

Default Naming Prefix

Sets a default filename prefix for exported reports.

Separator

Specifies a separator between the filename prefix and body.

Default Naming Body

Sets a default filename body for exported reports.

Separator

Specifies a separator between the filename body and suffix.

Default Naming Suffix

Sets a default filename suffix for exported reports.

Preview

Provides a preview of the final report filename.

 

Table View - File Naming

Field

Description

Default Naming Prefix

Sets a default filename prefix for exported tables.

Separator

Specifies a separator between the filename prefix and body.

Default Naming Body

Sets a default filename body for exported tables.

Separator

Specifies a separator between the filename body and suffix.

Default Naming Suffix

Sets a default filename suffix for exported tables.

Preview

Provides a preview of the final table filename.

 

Summary View - File Naming

Field

Description

Default Naming Prefix

Sets a default filename prefix for exported summaries.

Separator

Specifies a separator between the filename prefix and body.

Default Naming Body

Sets a default filename body for exported summaries.

Separator

Specifies a separator between the filename body and suffix.

Default Naming Suffix

Sets a default filename suffix for exported summaries.

Preview

Provides a preview of the final summary filename.

 

Export Options, General buttons

Field

Description

Make these the default settings

Saves the current settings in the Registry as the defaults for future Monarch Classic sessions. Note: When closing the current model you will be prompted to save the model changes. You must select Yes to save the tab settings as the defaults. If you choose not to save the model changes, the tab settings will not be saved as the defaults.

Restore from default settings

Restores the settings to the default values previously stored in the Registry.

© 2024 Altair Engineering Inc. All Rights Reserved.

Intellectual Property Rights Notice | Technical Support