If you are upgrading from ProScan 1.5, read this first!

 

Upgrading from ProScan 2.x to 3.x should be fairly painless.

 

BEFORE YOU ATTEMPT TO MIGRATE - do two things:

 

1)  Backup your application (more than once for safe keeping).

 

Also backup any of the ProImage template files, clw files or examples that you might have modified as the installer will replace them and it does NOT back them up!

 

2)  READ this guide

 

 

Migration Guide Tips

 

●Uninstall the old version of ProScan before you install the new one.  Some TXA filenames have changed and the uninstall process will get rid of the old ones automatically.

 

●You can get the new features into your app by re-importing the TXAs into your app to update the standard ProScan procedures to the new versions.  See this section on Migrating from ProScan 1.3 for specifics on how to reimport the TXAs.

 

Note that if you have customized the look and feel of the procedures you can skip this step and manually make changes as needed (comparing your code to the demo apps is a good place to start).  Both ways work.  Most of the "working code" is pulled into context via INCLUDE statements generated by the templates, but there are some small bits of code that may have to be done manually if you update what you already have.  Looking at the demo apps will show you what to include and where to put it.

 

Also note that there are now individual TXAs for import of some new procedures, or you can import a missing procedure from the demo app if need be.

 

●If you get compile errors with the new release, don't panic!  The ProSeries Utilities ( for Path and Registry manipulation ) have now all been wrapped in conditional code in the templates to give you fine control over when the declarations are generated.  You can find these controls on the "Misc Settings" tab of the templates.  In most all cases they are checked by default.

 

However if you get a compile error, it usually means that you need to enable or disable one of them.

 

Duplicate errors means that two controls are adding the same declarations (in which you uncheck one of them).

 

Errors about something being undefined usually means you need to check the box to enable the declaration.

 

See here for more details.