Navigation:  Using CGX - Step-By-Step >

Supported Output File Formats

Previous pageReturn to chapter overviewNext page

Supported Output File Formats

 

File ID

Description

Updateable

AXS

MS Access '2000 format MDB file

No(Adv) / Yes(Prem)

 

 

 

 

CSH

Commonly known as a "Comma Separated Values" (CSV) file. However the actual character used as the delimiter is based on the "list separator" character defined in the system's regional settings. Compatible with the manner in which Microsoft Excel processes CSV files.  A header row of all output field names is the first row in the file.

 

 

 

 

No

CSN

Same as CSH with no header row

No

 

CDH

Text file containing a user-defined delimiter of up to 2 characters with a header row of field names at start of file.

 

No

 

CDN

Same as CDH with no header row

No

 

MSQ

MS SQL '2000 and '2005 providing the appropriate SQL driver is found on the system when the program is run.

 

No(Adv) / Yes(Prem)

TBH

A tab delimited file with a header row of field names at start of file

No

TBN

Same as TBH with no header row

No

XLH

MS Excel '97-2003 format file with with the first row containing columns of all field names. All exported data will have a leading "apostrophe" in all fields indicating a text field when creating a new Excel file.

 

 

Yes

 

 

NOTES:

 

CSV files

 

There is no universal formatting standard for CSV files. CGX creates the processes CSV files based on the rules used by Microsoft Excel
CSV files created on systems with different "list separator" charcters defined via the Regional Settings will not be treated the same universally.
Multi-line fields in a CSV file (a file with a CSV extension) will be processed correctly by Microsoft products (i.e. MS Excel). If the same file is modified to have a "txt" extension, multi-line fields will not be processed correctly.

 

Microsoft SQL ('2000 & '2005)

 

Requires the SQL Workstation client components to be installed
MS SQL will only appear as an available option if the appropriate SQL driver is present
MS SQL '2005 required the SQL Native Client driver to be present
If both the MS SQL '2000 and SQL '2005 drivers are found, CGX defaults to the SQL '2005 driver (SQL Native Client)
To be able to process both SQL '2000 & SQL '2005 servers, the MS Backwards Compatibility update must be applied