Skip to main content
InSource Solutions

TN IT302 Reverting an InTouch Modern Type Application Back To A Classic Type Application

Count5.JPGInSource_Logo_Transparent (1).png




This article from InSource shows...

  • Author: Peter Farrell
  • Published: 12/22/2017
  • Applies to: InTouch Classic and Modern all versions


In the event that there has been an inadvertent conversion an InTouch application from a classic type to a Modern Application, the following steps may allow you to convert back to a Standalone if there is no backup. This is not an ideal or tested process, and it is not guaranteed to work every time for every situation.

Close all applications that you have running, and make backups before attempting the following steps.

1) Open InTouch Application Manager and right click on the Modern Application and select "DBDump". This will export the tagname dictionary to a .csv file. 

a. Tip: This uses an old interface, so instead of trying to use the navigation you will need to manually type the path, such as C:\DBDump.csv.

2) Open InTouch Application Manager again and create a new application, selecting the Legacy application type.

3) Double click on the new Legacy application to open it in WindowMaker, and once it finishes opening go ahead and close it. (We need to open it once to initialize some settings like resolution, version, etc.).

4) Reopen InTouch Application Manager. Right click on the new Legacy application and select "DBLoad", then point to the CSV file you created in step 1. This will import in your original list of tags.

5) Reopen InTouch Application Manager and open the Legacy Application in WindowMaker.
6) Go to the File menu and select Import > Windows and Scripts, then point to the modern application's folder.

7) You will be prompted to select the Windows and scripts you want to import. Press Select on each category and select All.

8) Put a checkmark in the "Conserve Placeholders" box. This will tell it to use the tags in the tagname dictionary (which you already imported tags into via DBLoad). If you don’t select this option the import process will assume this window is from a foreign app where the tags may not line up, and will prefix all the tag names with a ‘?’ and tag type specific place holder. IF you accidentally forget to hit the “Conserve Placeholders” option, it’s probably quicker to restart at step 2.

9) Click Import.

10) [OPTIONAL] – If your application used security for usernames/passwords, go to the Special menu, and to Security> Select Security Type, and select the appropriate type of security. If it was a standalone application, if security was used it would likely be the InTouch option. Close Window Maker at this point. Then go to the original modern application and grab the file called password.bin, and copy it to the legacy application’s folder (likely having to overwrite the existing file). This file contains the username/password/access level combinations.

In these steps we've imported in all of the tags (Step 4), the windows and scripts (Step 8), and potentially security logins (step 10).  If these steps fail to help you recover your application contact the InSource Technical Support group to discuss any remaining options.