Constructing a Batch Export File

A Batch Export command file can include many transactions to export many tables of the same or different types. A complete transaction must be defined for each table being exported. Collectively, the batch commands for a given transaction are composed of a set of parameters that describe the source table and the destination file.

Perhaps the easiest way to construct a Batch Export file containing multiple exports is to let SQLWizard create the batch commands for you. For each file you want to include in your Batch Export file, fill in the required information on an Export window. Then use the Save As command from the File menu to save the Batch Export specifications. After you have created these individual Batch Export files, use any text editor to copy and paste all of the batch commands into one file. Add comments as desired.

When construction a Batch Export file, keep in mind the following:

• Each transaction in a Batch Export file must begin with a name or label in square brackets to separate each set of batch commands. For example, you might want to enter the name of the table to identify the transaction, such as [EmployeeTable].
• Each Batch Export command must end with a semicolon ( ; ).
• You may include spaces and blank lines as needed to improve readability. The spaces and blank lines are ignored by SQLWizard.
• C-style comments (/*  comment  */) can be used in the specifications.
• All commands are case-insensitive. You may use any combination of upper and lower case letters. (For example, FORMAT= FIXASC; is the same as Format = FIXasc.)

Not all commands are required for all file types. For instance, the FLD_DELIMITER and REC_DELIMITER commands are required only for exporting to free-format ASCII files. The SPACE command is required only for fixed-format ASCII files.