Versions and Updating
NV2 is constantly under development in response to user requests for new features / functions and enhancements
that improve the user experience.
If you have not updated your version of NV2 within the last year, you are missing some of the most desirable features / functions / enhancements that have been added to date.
To view the details of the improvements provided by each new version of NV2, click on the version numbers listed to the right.
Each release of NewViews is uniquely identified by a release identifier. A release identifier consists of four numbers separated by dots in a form as shown below:
For example, the identifier "220.127.116.1150628" would represent version 2.1, service pack 3, and it was released on June 28, 2005. We further describe the meaning of each component of this (fictitious) release identifier below.
2.1 - Major and Minor Version Numbers
The first two numbers are the major and minor version numbers so this example represents NewViews version two point one (2.1).
The minor version number changes for relatively small changes to functionality and the major version changes for very significant changes. After downloading and installing a new version, some database processing may be required to upgrade a database to the new version. The processing occurs only the first time you open a database using the new version. The processing is generally automatic and you will be asked for confirmation before any processing is performed. After a database is upgraded to a newer version, it cannot be accessed using an older program version as NewViews versions only move foreward.
3 - Service Pack Number
This is the service pack number. The example represents the third service pack released for version 2.1.
A service pack does not introduce any significant functionality changes and does not introduce any incompatibility in databases used with prior releases. Typically bugs are fixed, performance is improved, and documentation and error messages are enhanced. Additional non-database functionality such as scripts or Tcl/Tk packages may also be included in the service pack.
The service pack number is reset to zero whenever the major or minor version number changes.
20050628 - Release Date
This is the date the release was added to the Q.W.Page web site for download. The date is in yyyymmdd format so the example was released on Jun 28, 2005.
It is Q.W.Page policy to release new service packs immediately when bugs are detected and corrected. The alternative is to accumulate a larger number of fixes until it is convenient to introduce a new release. Although the Q.W.Page policy results in a larger number of service packs, each containing fewer fixes, this makes the fixes available at the earliest possible moment. This policy is made possible largely because installing a new release is relatively fast and painless.
The release identifier is encoded into the program name for easy identification, and also provides the benefit that installation programs are sorted in the directory system according to the order released.
The installation program name includes additional information that identifies the hardware and operating system for the release. The same NewViews version or service pack may be released simultaneously on different platforms.
Program Version Compatibility
Multiple versions of NewViews can co-exist. A NewViews installation consists of the following:
A program such as nv201.exe
This is the NewViews program for version 2.01. It is in the installation directory.
A directory such as nv201.dat
This is the NewViews options data directory for version 2.01. It contains various printing templates, script options, and the registration file. It is a sub-directory of the installation directory.
A Windows start menu item such as NewViews 2.01
This is the Windows start menu item that is used to launch the NewViews workstation, server, and other functions for version 2.01.
When you install a new version of NewViews (i.e. the major and/or minor version number has changed), the installation does not clobber the things listed above for the previous version, but instead creates new ones identified by the new version number. So you get a new program, a new data directory, and a new start menu item, all clearly identified by the version. The old installation is not distrurbed and can continue to be used.
In fact, multiple versions of NewViews can co-exist. This allows you to upgrade different databases to new versions independently. As a practise, we recommend that when the version changes, you should process all databases to upgrade them to the new version. However, according to your judgement, there may be times when you want to upgrade in stages, and NewViews allows this by allowing the different versions to co-exist.
Eventually, when you no longer need to use an older version, because all databases have been upgraded, you should un-install it. This is accomplished by deleting the three things listed above for the particular version to be un-installed. You use the Windows explorer to delete the program file and the data directory from the installation directory, and then right-click on the Windows start menu item for the version and delete it. If you have saved the original installation programs for older versions, you can always re-install them if it is necessary to revive their functionality for any reason. Even when re-installing an older version, it can co-exist with newer versions.