Port to SQL > Step TWO (Application parsing)

This is a completely AUTOMATED Process which will Port your Application's TXA's and (optional) INCLUDE (CLW) Files to NORMALIZED SQL

Your existing application and CODE (and include files) will be synchronized to the NEW SQL Dictionary

If any CODE is found to be SQL NON compliant it will NOT be changed so as to generate at compile time an error BUT (when possible) a replacement SQL compliant CODE will be added as a COMMENT to HELP you (see below for an example)

This is the SECOND Main STEP in the Wizard Process

If you have several TXA's (multidll) or CLW files (includes) you can use MULTI SELECTIONS and let DMC handle them all.

Click on "Select your TXA or CLW File"

(If multiple selections then only the FIRST File will be displayed onscreen)

DMC will parse your (or each selected) TXA /CLW file and make your application and code SQL Compliant

This process is the longest one and can take upto several hours to complete (but generally is over in less than an hour)

The speed depends on the :

* number of LINES in your TXA

* number of Tables

* number of KEYS

* number of Column

as EACH line (or nearly) must be processed against ALL these elements!

You will have a NEW (set) of TXA - CLW files generated for you and placed in the SAME folder used in the FIRST Step

This folder now contains ALL your required files : DCTX - CLW (dmc globals) - TXA(s) PLUS a Legacy or ABC SwitchProcedure TXA to allow you to import in your DUAL application if this is your aim and to open TPS side or SQL side

(this procedure is an example "switch" procedure you can tweak to meet the licensing levels used in your application)

Copy these files to your working Clarion Folder and CREATE a NEW Application from TXA - the TXA MUST be in the same folder as your NEW Dictionary to "link" into it.

In this Folder you will find a sub folder (DO NOT DELETE) containing all TPS Files used during this process which can be useful

The ERRORS table is opened for you in a second instance of DMC (if errors exist) : it contains all your CODE changed to be SQL compliant ERRORS and NAME SWAPPING actions - for example

It will also contain all DMC COMMENTS on Best practice for SQL compliancy applied to YOUR code

The SQL scripts created and used are all contained in the "Scripts" TPS Table and can be used during end-user updating your application with the Runtime Engine.

This is the end of the second Step

DMC will close and reopen automatically and if you requested to Create Profiles (Data Transfer) it will take you to the Final Step of the DMC Wizarded port to SQL task

Click on "Transfer" to be taken to the Projects & Task Profiles Module with the created Project SELECTED up for you.

Click on "No" to Pause the Process (or cancel it in the next popup message)

If you Pause the process, the next time you open DMC the SAME STEP will be offered to you.

If ever you need to start this task again (after adding code in your TPS ORIGINAL application for example) (if NO changes are done to the DCT side) by clicking again in DMC on "Port my Clarion application to SQL" task in the Main Wizard window, you will find that DMC recognizes you had already processed the FIRST Step and offer you this screen (TXA parsing) :

Click on "I have already parsed the DCT... " button to acces the screen shown above and SELECT your TXA(s) and CLW(s) Files to parse them.