Export Formats and Format Specific Options

Use this format to export data to text or CSV (comma separated values) file. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Schema - specify schema of exporting

Standard Data are exported to a single output file (without using schema file).

ADO Data are exported to one file, and the schema (description of the fields) is stored in a separate file Schema.ini, which is located in the output folder and used for all such files from this folder. The format of the schema files is compatible with Microsoft Data Access Components (MDAC) specification, so such output files can be correctly opened in any application that uses ADO, including Exportizer. Notes Schema file is not created when data are exported to clipboard.

BDE Data are exported to one file, and the schema (description of the fields) is stored in a separate file file_name.sch, where file_name equals to file name of the main file but without extension. The format of the schema files is compatible with Borland Database Engine (BDE) specification, so such output files can be correctly opened in any application that uses BDE, including Exportizer. Notes Schema file is not created when data are exported to clipboard.

Field separator - specify character, which is used to separate fields in output file. If 'None' specified, no separator will be used, and the output file will have fields with fixed length. In fixed-length files, field data, which shorter than the field width, is completed by spaces.
Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents. MEMO fields can store large amount of text, so including them for this target format can significantly affect the results, especially if the text contains line or column breaks or other special characters.
Include column names - specify either to include the column names in target or not. Ignored for BDE schema.
Quote all fields - specify either to quote all fields in target or not. Using this option forces quoting all fields when more than one field is exported. This option is ignored for fixed-length files.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).
Quote character - specify a quote character. The quote character is placed around field data if the field data contains embedded field separator(s) or quote character(s), and when more than one field is exported. Embedded quote character is represented by a pair of consecutive quote characters. This option is ignored for fixed-length files.
Encoding - specify output encoding (e.g. ASCII, UTF-8 etc).
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Available only in Exportizer Pro and Exportizer Enterprise. Notes The format and field structure must be compatible with existing target.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to JSON file. Data are exported to a single output file as a series of JSON objects (one object per record), separated by commas. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Use raw data - specify either to use the raw data from the source or prepare them for proper use in JSON document. Using raw data can speed up the exporting process, but it can produce erroneous output when some characters, not valid in JSON, are present in the source data.
Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents. MEMO fields can store large amount of text, so including them for this target format can significantly affect the results, especially if the text contains line or column breaks or other special characters.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).
Encoding - specify output encoding (e.g. ASCII, UTF-8 etc).
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Available only in Exportizer Pro and Exportizer Enterprise. Notes The format and field structure must be compatible with existing target.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to Microsoft Excel workbook (binary). Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Notes
- All database records are written into one target sheet.

Use this format to export data to Microsoft Excel workbook (XLSX) (available only in Exportizer Pro and Exportizer Enterprise). Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from a table or SQL query, or when exporting data from a group of tables (multi-table export), specify a file name to export data to. In case of multi-table exporting, all tables will be outputted to one target file, each table on a separate Excel sheet.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Use raw data - specify either to use the raw data from the source or prepare them for proper use in Excel. Using raw data can slightly speed up the exporting process, but it can produce erroneous output when some characters, not valid in Excel or XML (internally, XLSX format is based on XML), are present in the source data.
Add autofilter - specify either to add autofilter for all columns in the target Excel document.
Rows per sheet - specify how many rows should contain an Excel sheet. If the number of passed rows in exporting procedure reaches this value, a new sheet is automatically created and the data output is continued into the new sheet.
Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Include images - specify either to include the graphics from BLOB fields in target or not.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to Microsoft Excel workbook (as XML) (available only in Exportizer Pro and Exportizer Enterprise). Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from a table or SQL query, or when exporting data from a group of tables (multi-table export), specify a file name to export data to. In case of multi-table exporting, all tables will be outputted to one target file, each table on a separate Excel sheet.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Rows per sheet - specify how many rows should contain an Excel sheet. If the number of passed rows in exporting procedure reaches this value, a new sheet is automatically created and the data output is continued into the new sheet.
Encoding - specify XML encoding.
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.
Floating-point numbers format - specify format for floating-point numbers. For example, 0.00.
DateTime format - specify format for DateTime values. For example, mm/dd/yyyy.
Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to HTML document. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from a table or SQL query, or when exporting data from a group of tables (multi-table export), specify a file name to export data to. In case of multi-table exporting, all tables will be outputted to one target file, and additional parameters like table title, table id, etc can be specified in Table Mappings.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Template file - specify a template file. In this case, the export procedure will enrich the template file with data from the current dataset and finally save the enriched template as a target file. Note: when using template, all export option will be ignored except template options, document title, row count limit, and record range.

Use raw data - specify either to use the raw data from the source or prepare them for proper use in HTML document. Raw data may be useful, for example, when it contains HTML code to be embedded into the target HTML document. Using raw data can speed up the exporting process.
Document title - specify document title.
Step no - specify the current export step. When using template, export can be performed in several steps, and this option lets the application know which dynamic expressions from the template must be calculated during this step.
Encoding - specify HTML encoding.
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.
Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Include images - specify either to include the graphics from BLOB fields in target or not. Images are exported as separate files into a sub-folder of the folder, where the target HTML file is located; the sub-folder will have the same name as the target HTML file (without extension) plus _filessuffix. If the application cannot determine the image format of some BLOB field, it ignores it. For large databases, including images may significantly decrease the export speed. This option is available only in Exportizer Pro and Exportizer Enterprise.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Target image format - specify format of target images. Possible values: PNG, JPEG, GIF, Bitmap, Metafile, Icon, <as source>; in the last case, the target image will be created in the format which was determined in the source, i.e. no image format conversion is done.
Create index file - specify either to create a separate index file for multi-table export. The index file will contain web links to all HTML files created during the export procedure.
Alternate row color - specify background color for every second row. The color must be specified in hexadecimal form, which is made up of sharp symbol (#), followed by three hex numbers, rr, gg, bb, that give values for red, green and blue, respectively; for example, #FF0000 represents red. If you don't want to highlight every second row, leave this field blank.
Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Available only in Exportizer Pro and Exportizer Enterprise. Notes The format, field structure, and encoding must be compatible with existing target.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to XML document. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Schema - specify XML schema

ADO Data are exported using ADO compatible XML schema. Such output .xml files may be then opened as regular tables using ADO interface.

Standard Data are exported using standard XML schema with metadata tag, which contains description of the fields.

Simple Data are exported using simple Exportizer XML schema.

XSL Data are exported using XSL schema, which is saved to the separate file with .XSL extension.

Encoding - specify XML encoding.
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.
Use CDATA attribute in text data - specify whether to use CDATA attribute in text data or not (only in Exportizer Simple schema). This attribute is used to prevent the data parsing.
Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Applicable only if schema is Exportizer Standard or Exportizer Simple. Available only in Exportizer Pro and Exportizer Enterprise. Notes The format, field structure, and encoding must be compatible with existing target.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Notes
In case of XSL schema, in addition to the main .xml file, a separate file with the same name and .xsl extension will be created and already existing .xsl file (if any) will be overwritten.

Use this format to export data to dBase (dbf) file. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Version (level) - specify dBase version (dBase level), to which data should be exported; possible values are 3, 4, or 5 (version 5 allows exporting BLOB data).
Encoding - specify dBase language driver (only for dBase IV and dBase V).

Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Notes

• No text data encoding is performed. Code page 437 is used by default (US English). So, if you export columns with text in native (non-English) encoding, you will need to specify correct language driver for the new .dbf table in external application.
• When exporting BLOB columns to dBase version 5 or above, in addition to main .dbf file, the separate file with the same name and .dbt extension will be created and already existing .dbt file will be overwritten.
• When exporting data to dBase version 3 or 4, BLOB columns are not exported.
• To export data to dBase format, you can also use Database export format; it uses installed database engine and therefore may work differently. It is recommended to try both formats and choose the one which suits best for you.

Use this format to export data to RTF (rich text format) file. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from a table or SQL query, or when exporting data from a group of tables (multi-table export), specify a file name to export data to. In case of multi-table exporting, all tables will be outputted to one target file, and some optional parameters can be specified in Table Mappings.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Include images - specify either to include the graphics from BLOB fields in target or not. If the application cannot determine the image format of some BLOB field, it ignores it. For large databases, including images may significantly decrease the export speed. This option is available only in Exportizer Pro and Exportizer Enterprise.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Alternate row color - specify background color for every second row. The color must be specified in hexadecimal form, which is made up of sharp symbol (#), followed by three hex numbers, rr, gg, bb, that give values for red, green and blue, respectively; for example, #FF0000 represents red. If you don't want to highlight every second row, leave this field blank.
Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to PDF (Portable Document Format) file. Export is done by Exportizer engine with direct file access and therefore is very fast. Note: currently, this format does not support characters other than Western Europe (Latin-1).

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Include images - specify either to include the graphics from BLOB fields in target or not. If the application cannot determine the image format of some BLOB field, it ignores it. For large databases, including images may significantly decrease the export speed.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Alternate row color - specify background color for every second row. The color must be specified in hexadecimal form, which is made up of sharp symbol (#), followed by three hex numbers, rr, gg, bb, that give values for red, green and blue, respectively; for example, #FF0000 represents red. If you don't want to highlight every second row, leave this field blank.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to SYLK file. Export is done by Exportizer engine with direct file access and therefore is very fast.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to Microsoft Excel workbook using OLE technology. Requires Microsoft Excel installed. Export may be slow for large datasets.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Alternate row color - specify background color for every second row. The color must be specified in hexadecimal form, which is made up of sharp symbol (#), followed by three hex numbers, rr, gg, bb, that give values for red, green and blue, respectively; for example, #FF0000 represents red. If you don't want to highlight every second row, leave this field blank.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to Microsoft Word documents using OLE technology. Requires Microsoft Word installed. Export may be slow for large datasets.

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents.
Include column names - specify either to include the column names in target or not.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Alternate row color - specify background color for every second row. The color must be specified in hexadecimal form, which is made up of sharp symbol (#), followed by three hex numbers, rr, gg, bb, that give values for red, green and blue, respectively; for example, #FF0000 represents red. If you don't want to highlight every second row, leave this field blank.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to SQL script file. It contains series of SQL statements, which can be used later to insert, update, or delete the data in database tables using special SQL tools. Export is done by Exportizer engine with direct file access and therefore is very fast. Note: BLOB and other binary fields are not exported.

Specific options:

File - when exporting data from a table or SQL query, or when exporting data from a group of tables (multi-table export), specify a file name to export data to. In case of multi-table exporting, all tables will be outputted to one target file, and some optional parameters can be specified in Table Mappings.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names and SQL table names can be specified in Table Mappings.

Statement type - specify type of SQL statements. For multi-table exporting, the value can be overridden for each individual table in Table mappings section. Allowed values:

Insert Application will create a series of INSERT statements.

Batch Insert Application will create a series of batch INSERT statements. Batch INSERT command allows to insert multiple rows at a time. Commit interval (see below) is used as a batch size. Notes Not all databases support this type of SQL statements. It is supported at least by Oracle, SQL Server, PostgreSQL, MySQL. Different databases uses different limitations on the batch size; the common recommendation is not to exceed 1000 rows; please also check your target database documentation.

Merge Application will create a series of MERGE or INSERT+UPDATE statements. It is required to specify key fields (see below) to match the rows. Notes The MERGE commands are generated only for target database types that support it (Oracle, DB2, Teradata, SQL Server); for other database types, the nearest possible solution is used (e.g. INSERT with ON CONFLICT clause for PostgreSQL); if the nearest possible solution is not known for the certain database type, the pair of UPDATE and commented INSERT commands is used.

Update Application will create a series of UPDATE statements. It is required to specify key fields (see below) to match the rows.

Delete Application will create a series of DELETE statements. It is required to specify key fields (see below) to match the rows.

PostgreSQL Copy Application will create a series of COPY statements. COPY statement is a very specific kind of statements to insert multiple rows in PostgreSQL database. It is often used in SQL dumps. Please make sure your SQL application can work with such statements.

Key fields (moved to Field mappings section) - specify matching fields to use in the ON (for MERGE statements) or WHERE (for UPDATE and DELETE statements) clause of the generated statements. This must be a name of a target field or a comma-separated list of several target field names. In Field mappings section, the key fields must be present among target fields.
Table name - specify table name to use in the generated statements.
Table description - specify description to be applied to the target table; currently, it can be applied to Oracle, SQL Server, PostgreSQL, and MySQL databases, and only with Add DDL option. If you specify <copy_from_source>, the application will try to use description of the source table (if any), but it requires more time to process.
Target database type - specify target database type, which lets the application know how to encode some specific data types in output file (for example, boolean, date, time, and timestamp). If the target database type is unknown, choose * Not specified *, in this case ANSI SQL standard will be used wherever possible.
Command separator - specify the separator between separate SQL statements; note, that the application always completes the separator by a line break.

Include MEMO fields - specify either to include contents of MEMO fields in target or not; in the latter case, a constant describing the field type will be used instead of the field contents. MEMO fields can store large amount of text, so including them for this target format can significantly affect the results, especially if the text contains line or column breaks or other special characters.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.

Initial actions - actions (commands) to add before DML statements.

Empty table - specify either to add TRUNCATE (if supported by target database) or DELETE statement into the output script before insert statements. Cannot be used together with Drop table and Add DDL options.
Drop table - specify either to add DROP TABLE statement into the output script before insert statements. Cannot be used together with Empty table option.
Add DDL - specify either to add DDL statement (CREATE TABLE...) into the output script before insert statements. Cannot be used together with Empty table option.
Add IF (NOT) EXISTS - specify either to include IF NOT EXISTS clause in CREATE TABLE statement, and IF EXISTS clause in DROP TABLE statement. It is supported only for PostgreSQL, MySQL, and SQLite databases. Must be used together with Add DDL and/or Drop table options.

Commit interval - specify number of source records after which COMMIT statement should be added; if 0 is specified, COMMIT statement is added once after the last record in the script. Ignored if target database type does not support COMMIT statement in SQL.

Encoding - specify the encoding of the target file(s).
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.

Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Available only in Exportizer Pro and Exportizer Enterprise.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.

Use this format to export data to relational database. Available only in Exportizer Enterprise and (partially) Exportizer Pro; the latter one can export only to ODBC data sources. Export is done by means of selected database engine (interface).

Specific options:

Database - specify a database to export data to.

Driver - specify target database driver (e.g. dBase, Interbase, Oracle, etc.).
User name - specify user name to connect target database (can be left blank, in this case application may ask it automatically when trying to connect the target database).
Password - specify password to connect target database (can be left blank, in this case application may ask it automatically when trying to connect the target database).
Table name - specify target table name.
Table description - specify table description to be applied to the target table; currently, it can be applied to Oracle, SQL Server, PostgreSQL, and MySQL databases, and only to table, which is created during the export operation. If you specify <copy_from_source>, the application will try to use description of the source table (if any), but it requires more time to process.
Commit interval - specify number of source records that should be exported before the transaction in target database is committed; if 0 is specified, commit is done after exporting all records. Ignored if target database does not support transactions.
Trim trailing spaces - specify either to trim trailing spaces and control characters in target or not. Applicable for char and varchar data only. Using this option allows to remove useless data and thus reduce the output volume, improve the target look for some destination formats etc.
Memory saving mode - specify either to use memory saving mode or not. The memory saving mode may be useful when the source or target tables have very large number of records, especially if target interface is ADO. This mode internally creates and executes series of SQL statements instead of opening the target dataset. In addition to memory saving, the improvements in performance may be achieved. Notes: This mode may work differently for different target database types/interfaces, therefore it is recommended to test it carefully before using on production systems.
Use SQL parameters - specify either to use SQL parameters in memory saving mode or not. Using parameterized SQL queries can significantly speed up the process and allows to export BLOB data for some database types/interfaces.
Batch mode - specify either to use batch mode or not (for FD connections only, which are available in Exportizer Enterprise). Batch mode reduces the target database workload and increases the speed of export drastically. The size of a batch equals to commit interval. Note: The record level logging may work differently in this mode.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Notes The field structure of the source must be compatible with existing target structure.

EMPTY+INSERT Target is emptied before inserting incoming rows; if target does not exist, it is created. Notes The field structure of the source must be compatible with existing target structure.

UPDATE The records in the target that match incoming records, are replaced with incoming records. Notes - The target must already exist and should have an index defined to match the records. - The field structure of the source must be compatible with existing target structure. - The fields in target, used to match the records (key fields of target), are not updated. - Use this mode carefully when the key fields (either source or target) can contain NULL values. - Use this mode carefully for multi-table exporting. - This mode may work differently for different target database types/interfaces, therefore it is recommended to test it carefully before using on production systems. Consider to use different combinations of Memory saving mode and Use SQL parameters options to find the best results.

APPEND+UPDATE The records in the target that match incoming records, are replaced with incoming records. Unmatched incoming records are appended to the target. Notes - The target must already exist and should have an index defined to match the records. - The field structure of the source must be compatible with existing target structure. - Use this mode carefully when the key fields can contain NULL values. - Use this mode carefully for multi-table exporting. - This mode may work differently for different target database types/interfaces, therefore it is recommended to test it carefully before using on production systems. Consider to use different combinations of Memory saving mode and Use SQL parameters options to find the best results.

DELETE The records in the target that match incoming records, are deleted. Notes - The target must already exist and should have an index defined to match the records. - Use this mode carefully when the key fields can contain NULL values. - Use this mode carefully for multi-table exporting. - This mode may work differently for different target database types/interfaces, therefore it is recommended to test it carefully before using on production systems. Consider to use different combinations of Memory saving mode and Use SQL parameters options to find the best results.

Key fields are used to match records for UPDATE, APPEND+UPDATE, or DELETE export modes. This must be a name of a source field or a comma-separated list of several source field names. In Field mappings section, the key fields must be present among target fields.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite or empty existing target for REPLACE+INSERT, CREATE_OR_REPLACE, or EMPTY+INSERT export modes.

Exporting data to user defined format. Data are exported to one file, which content is generated using dynamically calculated expression specified by the user. For each source record, the expression is calculated and the the result of the calculation is written to one target line. The expression should produce one-line string (i.e. result of its calculation should not contain line feed and carriage return characters).

Use this schema if you want to define custom format for target rows or apply some rules which are not available in other formats. For example, the following expression produces semicolon separated rows, and in each row, it concatenates two fields into one and converts another field to lower case:

dataset_field_val(1, 'app_tittle') + ' ' + dataset_field_val(1, 'app_version') + ' ; ' + lower(dataset_field_val(1, 'app_url'))

Specific options:

File - when exporting data from one table or SQL query, specify a file name to export data to.
Folder - when exporting data from a group of tables (multi-table export), specify a folder name to export data to. Each table will be exported to a separate file in the specified folder; file names can be specified in Table Mappings.

Line break - specify Line break style; if you choose Windows, then each line in the file will be terminated by carriage return and new line character (CR+LF); if you choose Mac, a carriage return (CR) will be used to separate lines; otherwise, Unix style will be used (LF).
Encoding - specify output encoding (e.g. ASCII, UTF-8 etc).
BOM - specify either to include BOM (byte order mark) when using Unicode encoding.

Export mode - specify export mode
(for multi-table exporting, the value can be overridden for each individual table in Table mappings section)

REPLACE+INSERT Target is created and filled with incoming rows; if target already exists, it is overwritten.

CREATE_OR_REPLACE Blank target (using appropriate structure) is created; if target already exists, it is overwritten.

APPEND Target is appended with incoming rows; if target does not exist, it is created. Available only in Exportizer Pro and Exportizer Enterprise. Notes The format and field structure must be compatible with existing target.

Ask before overwrite or empty existing target - specify either to ask the user to overwrite existing target for REPLACE+INSERT and CREATE_OR_REPLACE export modes.