The 'Major Release' version number: A number like "7.0", "8.5" or "10". Starting with v10 every new release will always be integer (like v15, v14, v13, v12, etc.)
Typically there's a new major release of the software once a year. With every major release, not only the .spf file format changes (always upwards compatible) but also the database files that come with the software (for "System DB" or "Designer DB", "User DB", etc.). Also several MS-Word templates that come with the software (and used to generate highly customizable Batch Sheets) as well the templates used to generate reports change as well. For that reason, a patch upgrade from one major release to the next will not work. A full installation must be applied to the target PC. Please note that even though a newer (major) release of the software (e.g. v13) can always be used to open design case files created with any previous release of the software (e.g. "ProjectX_v8.spf" created with v8.0, or "ProjectY_v95.spf" created with v9.5), once the opened file is saved again in the new format, it cannot be opened by an older version of the software. The same compatibility principle applies for software marked with newer build numbers versus older build numbers (even within the same major version family - see below).
A 'Build' number: Typically, a 2-digit number like "03", "10" or "17". There may be several releases (for the same major release number) where the build number may be incrementally changed. A new build typically will not add major new features to the software but may add some new features and will most certainly address issues encountered with previous builds. A new build number typically indicates an important new state of our current major release and users are strongly encouraged to upgrade to it. Detailed information on what is included in each new build number associated with our current release can be found in the Build Notes. As build number increases, the software will continue to open any files created with previous builds of the same major version, or any previous version for that matter. However, once a file is saved with this the new build software, a prior build will not be able to open it. That is why, for corporate or site license users to always have all the users of the software within your organization update at the same time.
The "Special Build" number (SBN): After the build number, there will be another four digit number, the 'Special Build' or SPB number: e.g. "1005" or "1312". This number indicates minor fixes that were done while the build number remained the same. Typically the SBN number may change if we have fixed a small bug or added a minor enhancement in a peripheral service of the software that will only be of interest to a small percentage of our users. Documents created with different SBN numbers can always be opened by the application as long it is in the same family of major release and build number.
All major files that make up the installation files of each release are also stamped two sets of numbers (see Installation Files) that can be seen if you right-click over any of the files (as viewed with the File Browser of Windows) and then select "Properties".
- Product Version Number; e.g. 12, 0, 01, 1000 (the first two numbers represent the Major Version Number, - yellow highlight below - the third number is the Build Number, - green highlight below - and the fourth number should match the Special Build Number or SBN - purple highlight below - ).
- File Version Number; e.g. 12, 0, 01, 1000 (same as above).
These numbers are always reported by the software if you select Help / About... from the main menu (see below):
Please note that if you have a "special edition" release of the software (e.g. "Site Ed." or "Academic Ed.") it is mentioned right next to the name of the application (see grayed field above).
Once you complete an installation (or upgrade) and in order to make sure you are running the latest build, please view the release numbers reported by the software or please check to verify that the executable files are marked as expected (also check the topic: How to Verify that I am Running the Latest Build).