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 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 Download

The Caliach Vision installer can be downloaded from the support section of www.caliach.com. The name of the installer contains reference to the major version and the operating system. Typically in the form CaliachVision-4.10-windows-installer.exe. In the case of Windows it is an executable that you can run. In the case of Mac OSX it is a disk image file that, if opened, will mount on you desktop to reveal an installer application to run. Otherwise the installer operates identically on both operating systems.

Caliach Vision and its associated folder structure and ancillary files are all installed from a single installation file which also contains both Runtime and Design editions of Omnis Studio. To install, follow the instructions in the installer wizard. You can choose to install just the runtime Omnis Studio or both Runtime and Design editions. These too will be installed within the Caliach Vision folder, typically C:\CaliachVision-4.10 or Applications:CaliachVision-4.10. To ensure everything is tidy, the installer is not designed to place the executable in C:\Program Files on Windows.

If you are re-installing on top of an existing installation of the same major version, files will be overwritten, but files added since the first installation will not be removed.

You may then want to copy accumulated valuable files such as those in Archive, Graphs, Export, etc. from the old version folder structure to the new, so that you don't loose anything valuable.

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 class changes you have made and Strings you may have customised.

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 5.04. Help data last modified 7 Oct 2013 07:08. No class.