Projects & Profiles > Export a Project

EXPORTING a Project (for the Runtime Engine)

When you are satisfied of all the Profiles in a Project - use the create NEW Project from Top Main Frame to store them all in a specific Project and to move them Up or Down if a special Order is required

Then you can use the IMPORT-EXPORT button to generate all necessary files required to be shipped to your end-users machines

1. Select the PROJECT

2. Click on Import - Export

3. Click on Export

4. Define a Project NAME (can be anything you wish)

5. Click on EXPORT : DMC will create a NEW folder as per the NAME entered and generate in this folder ALL relevant TPS (and ini) Tables required to be shipped to your end user clients

6. A Temp view of the Exported Project will be displayed for you to see and check all was properly done for you

7. Click on the Reset View Button to restore your own Projects and Profiles

8. DMC will open up for you a new window of Windows Explorer in the created FOLDER where the generated Files are located for you to copy them ....

DO NOT TOUCH those files as they contain ALL your end users require to run this Project when called from your application (with the help of our template TXA and TXD files shipped in the demo installer)

(you can open the "link" table generated - (dmcrt_odbc.tps) check for the password in your template documentation - to change some settings there but be CAREFUL to what you do there)

an example of a manual change at your end before shipping the files :

your sql server is localhost and your end users are a distant machine (or the other way round)

open dmcrt_odbc table and locate all the columns called NAME and copy paste the proper connection string there (source and /or destination)

do the same for the column called server_s or server_d

save and close

do the same changes in the maptet.tps tables (profile headers) in the column called SourceConnectionString and / or DestinationConnectionString

save and close

NEVER touch the other Tables

you could change also the PATHS to tables like this but I is much EASIER to do it directly in your application as explained in the demo application and RT help file!