If ODBC is chosen as the Export type, a drop-down list is displayed below the Output Type pull-down menu containing a list of ODBC data sources defined for the current output destination (LOCAL by default, a connectable Arbutus Windows Server if chosen). There are additional checkboxes provided to control the ODBC sources displayed:
| | Show Data Sources (Default) |
| | Show Drivers |
| | Show FileDSNs |
If ODBC is selected and the output destination is changed (i.e. changing from LOCAL to an Arbutus Windows Server), the list of ODBC data sources will automatically be re-populated.
When exporting via ODBC to relational tables, the Append option can be used.
When exporting columns containing UNICODE data (UTF 16 Little Endian only) via ODBC, the data will be exported as UNICODE (UTF 16 Little Endian only).
Output to ODBC sources (consistent with exports to EXCEL and ACCESS) allows the user to specify a table name. If a table name is not specified, then the open table name is used. If the user manually includes a schema or subsystem in the specified table name via the Export dialog or on the command line (e.g. SUBSYS.DBO.NEWTABLE), everything but the table name is ignored.
Note: The Export command does not currently support specifying subsystem or schema names. They can only be specified on the command line using the Qualifier parameter. For more info see Command Mode Syntax.
The output database name for relational data sources is set to Default and may not be changed when the Output Type is a relational data source (such as SQL Server, Oracle or DB2). For non-relational data sources (such as Excel or Access), if output is to a data source and the data source has an associated file, the associated file name is shown in the dialogue and cannot be changed. If there is no associated file, or the output is an ODBC driver, the user must supply an output file name.