 |
|
|
 | Data Transfer Usage Examples |  | Data Transfers | Data Export in 602SQL |  |
The design automatically generated by the wizard is suitable for most data transfers. The general description discussed here has one advantage. You can omit columns, rename them, and do type conversion using this method.
Each row of the detailed description tells the server how each source column should be handled during the transfer. Columns of the detailed description are modified according to the selected source and target data.
You specify the value to be transferred in the first column. If you are transferring from 602SQL, you can specify a column name or a expression. If you are transferring from a DBF file, specify the field name (usually a column). If you are transferring from a text file, the first column is filled with a fixed number of entries (columns).
The next column specifies where the transferred value should be inserted. When transferring into a text file, you must fill the sequence number of the target entry (column). If you are transferring into an existing table, select one of the columns. If you are transferring into a non-existent table or a DBF file, specify the name of the column (field) that should be created.
The other columns are only used when the data is transferred into a file or a non-existent table.
If the output is not a text file, select the column type to the left. Types from 602SQL or the DBF format will appear for your selection.
The last column serves for specifying the length (width) of the data (field) source column currently being created. This is relevant for all fields (except for memo) in the DBF format and for character string types in 602SQL. This specifies the column width in the column format. This is usable in the CSV format only if it is no zero. It specifies the maximum length of an item.
The corresponding type conversion is automatically performed when transferring data (except for 602SQL to 602SQL transfers). If the conversion cannot be done, an empty value will be transferred. You can explicitly specify the conversion when transferring from 602SQL using the expression in the first column.
You can only import data in the 602SQL internal format (*.tdt) into an existing 602SQL table. You can only export data from a 602SQL table or query result in the 602SQL internal format (*.tdt). All other combinations of input and output are allowed except the above.
If the 602SQL table that is receiving data during an import already contains data, the imported records will be inserted after the existing records. This occurs for all formats.
| Data Transfer Usage Examples | | Data Transfers | Data Export in 602SQL | |