Upgrading Caliach Vision to a New Version

Document path Reference Contents > Introduction > Upgrading Caliach Vision to a New Version

When a new version of Caliach Vision is supplied you will have to copy your custom classes into the new OpenVision.lbs that will be installed with the new Vision version.

Caliach has a structured version control policy. The version number increments in three parts, as follows.

The first number left of the decimal relates to the major license release, as in V1. or V2. These will need license renewal and may need major changes to any custom features you have.

The hundredth decimal relates to the structure version, as in V1.12 and V1.13. These two versions may have different data structures and may need minor changes to custom features you have.

The final two digits relate to the maintenance version, as in V1.1203. This indicates that the program is running with number 3 maintenance update of V1.12. Maintenance upgrades are usually in the form of a ProgCode.upt update downloaded across the Internet.

When Caliach releases a new structure version of Caliach Vision (i.e. VN.NN change) you will need to install all workstations with the new version of Caliach Vision from a CD or after downloading the full installation from the Internet.

Upgrading an Existing Installation

When you have a currently running multi-user installation of Caliach Vision, the overall upgrade process should be as follows:

Installation from a CD

Install Omnis Studio before installing Caliach Vision.

Caliach Vision and its associated directory structure and ancillary files are all installed from a single installation file, SetupVision.exe on Windows and Install Caliach Vision on Macintosh. To install, follow the instructions which came with the CD.

If you are re-installing or upgrading, the installer will protect potentially customised files, such as OpenVision.lbs and Strings.stb by copying them to a Saved directory.

Discard any ProgCode.upt (as opposed to .usa) file from your data directory, as this relates to upgrades of an older version of Caliach Vision.

Upgrading your Customisation with a Full Installation

Always keep a backup of your custom classes by holding a secure copy of your edited OpenVision.lbs file and ProgCode.usa file, and fully document any file classes changes you have made.

Place your previous ProgCode.usa file into your Custom directory, if it is not already there.

Note NOTE: If you are upgrading to Caliach Vision V1.10xx or later from V1.0xxx you should read the special note Upgrading Caliach Vision to V1.10 from Earlier Versions.

Launch the new Caliach Vision using the design edition of Omnis Studio. You should at this stage avoid attaching to your Main Business Data. Attach to TrainingData.df1 which you will find in the Data directory of your Caliach Vision installation.

See also: -

Compiled in Program Version 3.10. Help data last modified 13 MAY 2005 11:13. No class.

Document path Reference Contents > Introduction > Upgrading Caliach Vision to a New Version