|
|
Version - Sub-version - Release |
||||||
| The Pro/3 version number consists of three numbers: the version number, the sub-version number and the release number. Generally, different releases (within the same version) relate to different compiles of the system i.e. with minor bugs removed and/or minor functional enhancements (but without changes to the standard knowledge source files). A KB is always compatible between different releases. Different sub-versions refer to more than minor changes to the system, and may or may not come with changes to the standard knowledge files. It is usually possible to automatically upgrade a KB for a new sub-version. As a standard rule, always reload the standard knowledge files when you open a KB under a new sub-version. New versions refer to major changes to the system, and it is usually not possible to upgrade a KB from one version to another. Instead you will have to reload all knowledge from source files (which may or may not require manual editing). | ||||||
|
Before you install the new version of Pro/3 |
||||||
| If you have existing knowledge bases you plan to upgrade to the new version, then make a full source level backup of the contents. You might need these source files in case you are unable to automatically upgrade the existing KBs. It is also a good idea to make a copy of all Pro/3 directories before installing the new system, as well as copies of existing KBs. This will e.g. enable you to re-generate source files and/or look up knowledge in these KBs. | ||||||
|
Upgrading KBs |
||||||
| Pro/3 will discover when a KB created under an old version is attempted opened. Necessary updates and changes to the KB will be carried out if at all possible. Pro/3 will also prompt you to reload standard knowledge files (i.e. if new release). | ||||||
|
Upgrade Notes |
||||||
|
||||||
|
Release News |
||||||
|