GainSeeker® 7.502 Maintenance Release

Description

This document lists the revisions made to GainSeeker Suite in the maintenance release 7.502.5. If you are currently using version 7.502 or greater and are experiencing one of the issues listed below, you may download this release. See the download instructions at the bottom of this document for running this password-protected installation. If you are not currently using version 7.502 or greater you will experience problems if you apply this release.

All modules

Resolved issues addressed in this service pack:
A. When using the SPC Planner to set or change which user or group names were assigned to a planned session, the changes to user names were not stored. This could happen when running GainSeeker on a SQL Server 2005 database, or when the convert.db file contained the line "useqry=1". This issue has been resolved.

The following issue was fixed in service pack 7.502.4 and is included in this release:
B. When one user logged in to GainSeeker, all GainSeeker licenses were filled, so that multiple users could not be logged in to GainSeeker at the same time. This could happen when running GainSeeker on a SQL Server 2005 database, or when the convert.db file contained the line "useqry=1". This issue has been resolved.

The following issue was fixed in service pack 7.502.3 and is included in this release:
C. When running GainSeeker on a SQL Server 2005 database, logging in to one of the GainSeeker modules could generate an error message and prevent the module from being launched. This issue has been resolved.

The following issue was fixed in service pack 7.502.2 and is included in this release:
D. On a SQL Server or Oracle database, error messages could be generated during SPC data entry if the current standard was configured to write to monitor files "For all data" or for "Data without failures" and a data record without failures was entered.

On a SQL Server database, this error message was reported as follows: Error 8180: 37000: [Microsoft][ODBC SQL Server Driver][SQL Server] Statement(s) could not be prepared.

On an Oracle database, this error message was reported as follows: Error 904: S0022: [MERANT][ODBC Oracle 8 driver] [Oracle 8]ORA-00904: "LASTREC": invalid identifier

The following issue was fixed in service pack 7.502.1 and is included in this release:
E. If traceability labels are displayed on the x-axis (Chart Options menu, Display Options) and the number of retrieval data points is greater than the number of displayed data points (Session menu, Retrieval Setttings), then after a new data point is entered the traceability labels are shifted too far to the left, which also results in blank labels on the right side of the control chart.

Solution

Download the release GS7502_5.exe (12 Mb)

A password is required to uncompress files after downloading. To receive your password, please contact our Customer Service Department at 574-533-0571, ext. 2. Refer to incident number 15995 when you call. You may also email us at support@hertzler.com. This will allow us to ensure your current system is compatible with this release and provide you with the password.

We recommend that you print this page to have with you during installation, and for future reference.

After downloading the file...

All GainSeeker users should exit GainSeeker programs and log off the network. Copy the file (GS7600_1.exe) into a temporary folder and run it. When prompted, enter the password you received from our Customer Service Department. (Please note: the password is case sensitive). Select the folder where GainSeeker 7.600 is currently installed to unpack the installation. If prompted to overwrite files that already exist, click "Yes".

If you have any problems or questions regarding this procedure, contact our Customer Service Department at 574-533-0571, ext. 2.