The Dbase connector is an object that is used to export data to DBase III, DBase IV and DBase 5 and VFPOLEDB.1 files (*.dbf).
After adding the connector to the ETL task workspace, set basic properties and export options. The connector input and output can be also edited, and error handling parameters can also be set.
In basic properties object name, identifier and comment are set.
The Export Options page is used to specify a database file for data export.
Specify consumer directory containing Dbase files, and driver for corresponding Dbase version.
Selecting the Clear Consumer Before Loading Data checkbox enables the user to delete all information from the consumer before data loading.
The page is available only in wizards of consumer objects and in the Copy Data object. The page is displayed for repository consumer if a table or document object is selected as a data consumer.
Determine behavior of the object on error occurrence:
Select the action executed if errors occur in the drop-down list Action Performed on Error Occurrence:
Stop Task Calculation. If export error occurs, ETL task runtime is stopped.
Skip Only Incorrect Records. Incorrect records are skipped. This item must be selected if it is not essential whether all records are present
Skip All Records In One Transaction. All records of the transaction where an error has occurred are excluded. Select this option in case when it is necessary to divide records collection into transactions to get all data without exceptions within these transactions
NOTE. The Skip All Records in One Transaction option is not available for the Excel (*.xlsx) consumer.
On selecting the Stop Task Calculation and Skip Only Incorrect Records actions, the task is also divided into transactions, and the specified number of records affects speed of task execution.
A file used to store skipped records can be specified on selecting the Skip Only Incorrect Records or Skip All Records In One Transaction actions.
In the Save Skipped Data to File box select the file to save skipped records. If there is no file with such a name, it is created automatically.
Skipped records are stored in the specified file if the Skip Only Incorrect Records or Skip All Records in One Transaction actions are selected for task errors handling. Data is deleted in the existing file before loading new data to it.
Available file formats:
Encoding: Unicode.
NOTE. If on exporting there were no skipped records, the text "??" is written to the file. This means an empty Unicode file with the Win encoding.
Rows separator: {Carriage Return}{Line Feed}
Fields separator: ; (semicolon)
Text terminator: "" (double quotation marks).
NOTE. By default the following file name is formed: <consumer identifier>_skipped records.csv.
Each skipped record is registered in the ETL log as a single record containing the number of skipped record, error text and field. If all records within transactions are skipped because of one error record, the log displays this reason in the Description field.
NOTE. The screenshot represents edit wizard for the Repository data consumer.
To set a list of fields and link to input, use the Edit Input page.
The following parameters are available on the page:
NOTE. The screenshot represents edit wizard for the Repository data consumer.
To set a list of fields and output link, use the Output Edit page.
The following settings are available on the page:
NOTE. The screenshot represents edit wizard for the Repository data provider.
See also: