This topic describes resolutions or solutions in GainSeeker versions 9.5 and 9.5.1 and corrections to the Online User Guide.
In the GainSeeker Charts, GainSeeker Inspections, and PC Collect modules, the statistic for Count subgroups within 2 sigma was erroneously labeled "Count subgroups within 3 sigma". This issue has been resolved. (Issue: GAIN-4476)
On a database with expanded traceability fields (over 30 characters long), editing a traceability list and importing values from a .csv file would erroneously import only the first 30 characters of each value. This issue has been resolved. (Issue: GAIN-4556)
If a Note contained an invalid file path or filename, attempts to edit that Note would generate errors. This issue has been resolved. (Issue: GAIN-4532)
Adding or editing an item in the SPC Event list was erroneously recorded in the Audit Trail as adding or changing a DMS Event. This issue has been resolved. (Issue: GAIN-4548)
When the list of inspections or planned inspections was displayed, clicking or double-clicking several list items or buttons while waiting for the inspection to load could generate error messages. This issue has been resolved. (Issue: GAIN-4513)
Documentation for inspect.cursubi.rating(idx).getcolor incorrectly stated that this command would always return the colorname if inspect.cursubi.rating(idx).setcolor had been used to set the colorname. The Python editor code-completion help has also been updated to reflect that this typically returns the color in hex format. This issue has been resolved. (Issue: GAIN-4579)
Previous versions incorrectly allowed you to create or import two scripts with the same name but different capitalization. This issue has been resolved. (Issue: GAIN-4507)
Saving SPC charts in a Desktop failed to save the "Skip retrievals with no data on multiple charts" setting. This issue has been resolved. (Issue: GAIN-4582)
On a Dashboard Grid, sorting a column of numeric values with the currency symbol (such as $) would sort them as text instead of as numbers. This issue has been resolved. (Issue: GAIN-4561)
In some cases, when a Multiple Charts window displayed control charts for multiple standards, single-clicking a point on the chart displayed a tool tip with the wrong date/time stamp and double-clicking a point on the chart highlighted the wrong row of the multi-standard data table. Date/time stamps have been removed from the single-click tool tips, and the remaining issues have been resolved. (Issue: GAIN-4555)
On a Pareto chart with bars sorted by a traceability field, starting the drill-down wizard and then clicking the Next button could display an error or incorrect results. This issue has been resolved. (Issue: GAIN-4552)
When creating a new dashboard retrieval, canceling the new retrieval before saving it would still save a blank retrieval with the name of the new retrieval. This issue has been resolved. (Issue: GAIN-4515)
When displaying an SPC Pareto chart, sending the chart to HTML displayed DMS statistics below the chart, and the right-click menu included tools for DMS data. These issues have been resolved. (Issue: GAIN-4490)
When viewing an OEE Detail chart, right-clicking the chart did not display the Group By menu option. This issue has been resolved. (Issue: GAIN-4499)
Importing users from a .csv file allowed you to have multiple users with the same first 20 characters, which could cause problems for legacy modules. This issue has been resolved. (Issue: GAIN-4538)
If an XML import file contains a tag such as “<Event />" instead of the usual format "<Event></Event>", selecting the file to import would generate the error message "There was an error while reading the file: The method or operation is not implemented." (A file could contain this type of tag if, for example, the data being exported contained an Event code that does not match anything in the Event list.) This issue has been resolved. (Issue: GAIN-4570)
In the instructions for installing the GainSeeker client, the list of new tables that are created when upgrading from older versions of GainSeeker should have included the SCRIPTARCHIVE table (which was added in version 9.3.2), and the list of table names you can customize for each configuration should have included HSISCRIPTS and SCRIPTARCHIVE (which could use different names in different configurations starting in version 8.8). This issue has been resolved. (Issue: GAIN-4457)
When editing an SPC standard and changing the X-bar and Performance Chart Scaling (on the Scaling tab), setting the Upper value less than or equal to the Lower value and then clicking Set Interval would crash the current GainSeeker module. Also, if you set the Upper value equal to the Lower value, GainSeeker allowed you to save this change which would render the X-bar chart unreadable. These issues have been resolved. (Issue: GAIN-4472)
The GainSeeker Inspections and PC Collect modules would crash when trying to read values from an OPC DA server or browse an OPC DA server. This issue has been resolved. (Issue: GAIN-4502)
When trying to group SPC data by date/time change, the list of date/time groups was not displayed. This issue has been resolved. (Issue: GAIN-4470)
When retrieving data shortly before the Start of Day setting, the date periods Current Shift and Previous Shift returned incorrect start and end date/times. This issue has been resolved. (Issue: GAIN-4498)
When viewing an SPC data table, opening a Pareto chart of that data and then changing its Bar Orientation setting to Vertical would incorrectly change the Pareto to display one "Defect Count" bar. This issue has been resolved. (Issue: GAIN-4386)
When editing a dashboard Chart control for a DMS retrieval, changing the Chart type property displayed the DMS chart types in the wrong order. This issue has been resolved. (Issue: GAIN-4411)
When editing a dashboard Defect Trend Wizard control with the DesignData property set to "True", the row colors configured by the TrendDecreasingColor and TrendIncreasingColor properties were not displayed. This issue has been resolved. (Issue: GAIN-4418)
After right-clicking an SPC control chart and selecting Resume Variation Wizard or Previous Variation Wizard, hovering over the Significant Difference or Rank for any row failed to display the F-test and t-test results for that row. This issue has been resolved. (Issue: GAIN-4478)
When an SPC subgroup contained a blank (missing) value that was not the last value in the subgroup, any non-blank values that followed in that subgroup were erroneously excluded from the calculation of normality statistics (Distribution, A1, A2, Kurtosis, Kurtosis test, M1, M2, Non-normal area, Skewness, Skewness test, Spread used, Zl, Zl factors, Zl non-normal, Zl SSD, Zu, Zu factors, Zu non-normal, and Zu SSD). This issue has been resolved. (Issue: GAIN-4481)
In a sub-inspection that contained a DMS Standard test with a blank DMS Part Number property and a Defect List test with a Defects property that specified a different process, the list of Part Numbers was erroneously filtered for standards that used the inspection Process property instead of the process set by the Defect List test. This issue has been resolved. (Issue: GAIN-4281)
Running a sub-inspection sometimes generated an "Animation failed" error. This issue has been resolved. (Issue: GAIN-4362)
If a sub-inspection included an SPC chart for a Numeric Input test, both Use numeric input standard and Apply Filter from numeric input were selected in the Chart Options, and the Numeric Input test was present but not visible, changing a Traceability value for the sub-inspection would generate an error. This issue has been resolved. (Issue: GAIN-4495)
When a date/time value was provided to the inspect.datetime or inspect.cursubi.datetime().datetime command, GainSeeker would display an error message and halt script execution only if the data type was invalid. However, if the data type was valid but the value was not recognized as a valid date/time, GainSeeker failed to display the error message or halt script execution. This issue has been resolved. (Issue: GAIN-4442)
Documentation for the inspect.cursubi.checkbox(idx).note command was missing from the documentation. This issue has been resolved. (Issue: GAIN-4471)
Clicking the File menu, pointing to Programs, and then clicking GainSeeker Lists opened the Assign Inspections utility instead of the GainSeeker Lists utility. This issue has been resolved. (Issue: GAIN-4466)
In SQL Utility, executing a SELECT statement for a column with a byte array data type such as timestamp would generate an error if a value in that column did not resolve to a valid image. GainSeeker now checks byte array values and converts values that are not valid images to display "System.Byte[]". This issue has been resolved. (Issue: GAIN-4474)
Exporting SPC data would hang if it encountered a data value that is NULL. This could happen if a data record's subgroup size is greater than 8, but data measurements 9 and above are missing because the corresponding record in the VDAT_AUX table is missing. This issue has been resolved. (Issue: GAIN-4485)
Exporting SPC or DMS data would hang if it encountered an invalid date/time stamp. This issue has been resolved. (Issue: GAIN-4485)