From the Tasks Menu, Select a Task page you can select to "Clone a table" (one table at a time). Multiple tables can be cloned using "Clone a SQL DB or a Dat-Tps FOLDER" option.
Select the format - driver of the Source Table you want to Clone and you can then select the table, enter the Password if required and View the table structure.
BEFORE starting a Clone task you can use the "SQL Normalization" OPTION (from the Information Bar) so as to apply any Predefined settings
You will have exactly the same options as in Transferring Data
The source Table will be read and it's Structure and Data stored for you, then an SQL script will be created depending on the selected driver. At this stage, the table is not created. A Tab called SQL script Editor will open up for you to see and modify the script if desired.
If the Table already exists in SQL, you will be prompted to DROP it (or not)
If a DATE column is detected (in a TPS or DAT Table), then DMC will offer to change this data type in SQL
When you press the "RUN" button the process resumes and the table is created and read as destination (you can of course apply all modifications required before clicking on "Run")
Then all normal processes are done to let you finally have the full mapping tab opened for you to transfer your data as you wish like in normal data transfer
When you reach the mapping Tab screen after a successful cloning, and want to stop there (NO transfer of data done) then simply use the top frame "Close module" button.
VERY IMPORTANT INFORMATION (for DEMO version ONLY): you are ONLY allowed to do create 10 Tables cloned to SQL in demo mode and no extension normally can be given to this limit (different from TPS cloning)
BUT : if you clone TO or FROM our SQL's Test Server then you have NO LIMITATIONS
For example you want to test cloning a TPS table to Ms SQL : clone it to OUR Test server (connection shipped by default with DMC) and you can repeat this task FREELY
THIS TASK IS RUNTIME ENGINE COMPLIANT
If you need to perform this task on your clients computers , then SAVE it as a Profile when all is defined and use the Runtime Engine to run it from your application
The different settings on source - destination Folders (even Table Names) plus some ODBC settings like User Name and Password can be changed dynamically from your application to meet your requirements