This topic describes resolutions or solutions in GainSeeker version 10.2 and corrections to the Online User Guide.
When grouping data and the Statistical outliers setting is set to Out of Control, runs, trends, and zone violations excluded, the software would sometimes report a "There is no row at position [x]" error. The error would only occur if there was more than one group and a run was found in the data. This issue has been resolved. (Issue: GAIN-4812)
When a desktop was stored with a sorted column but the column was not being displayed, an error occurred. This issue has been resolved. (Issue: GAIN-4842)
Exiting Dashboard Edit mode usually resulted in a message asking the user if they want to save changes even if no changes were made. The frequency of this message has been reduced (but is dependent on the .Net Framework version). (Issue: GAIN-4844)
When two people would edit a custom statistic at the same time, an invalid last edit user name and last edit date could be stored. This issue has been resolved. (Issue: GAIN-4791)
Replacing defects on a Defect List test using the inspect.cursubi.defectlist(n).defects Python command would show an incorrect list if the sub-inspection was loaded additional times without exiting the inspection. Subsequent loads of the defect list would show the original defects and the new defects. This issue has been resolved. (Issue: GAIN-4834)
Best practice found during testing: do not use the following Python commands in a loop
file.xls.columncount, file.xls.lastcol, file.xls.lastrow, file.xls.rowcount
Instead, set it to a local variable and use that variable in the loop.
When setting the samplesize on a Defect List through a python script, the wrong sample size could get stored. This would happen when the EnableSampleSizeAndNCU property was set to false and the SampleSize property was set to a value. This issue has been resolved. (Issue: GAIN-4787)
When setting the value of a Pass/Fail/NA test to NA through a python script but the NA button was disabled, the error message was misleading. The error message has been updated to be more accurate. (Issue: GAIN-4824)
When using a Traceability test and the Traceability property is set to Text Entry, an unnecessary and erroneous database query was executed. This issue has been resolved. (Issue GAIN-4840)
Inspection and Sub-Inspection names with an ampersand (&) character did not display correctly on several dialogs. This issue has been resolved. (Issue GAIN-4869)
The .itemtofront and .selectitem Python commands for the inspect.sidepanel object did not always set the focus correctly.This issue has been resolved. (Issue GAIN-4876)
The Standard Utility function of GainSeeker Utility used the Log changes to data audit trail setting instead of the Log changes to standards audit trail setting when determining when to log changes to the Audit Trail. This issue has been resolved. (Issue: GAIN-4759)
In previous versions of GainSeeker, the Audit Trail would give errors if too many entries were found. Now, only the most recent 5000 entries that pass the filter are displayed. (Issue: GAIN-4781)
The Export data function of GainSeeker Utility exported incorrect data when using the Fill list option and the Select All button. It exported the entire list of standards instead of the standards that matched the fill list criteria. This issue has been resolved. (Issue: GAIN-4804)
When importing data in XML format that was exported prior to version 8.8, an error would occur if the XML file contained bypassed data. The error message states "Input string is not in a correct format." This issue has been resolved. (Issue: GAIN-4792)
The XLS2TXTN.exe utility has been optimized and now runs from 3 to 10 times faster, depending on the size of the file. (Issue: GAIN-4800)
The Define Columns function when exporting notes in Note Manager did not work correctly for traceability fields over 99. This issue is resolved. (Issue: GAIN-4837)
Fonts and Colors were not being saved correctly when set as a chart override of a retrieval (Settings tab). This issue has been resolved. (Issue: GAIN-4721)
The main window has columns for Name, Last Edited, Last Edited By, and Last Used. These columns can all be sorted by clicking on the column header. The two date columns (Last Edited and Last Used) did not sort correctly. This issue has been resolved. (Issue: GAIN-4761)
When saving a report to a file and a file by that name already exists, the application does not overwrite the file but creates a new file with a number scheme appended to the file name. This issue has been resolved. (Issue: GAIN-4793)
When using the command line parameter ConnectString to specify a database connection when starting a GainSeeker application, the specified connect string was not always passed to other GainSeeker applications that were loaded from the original application. This issue has been resolved. (Issue: GAIN-4794)
When using the File menu option to Change Configurations, selecting a configuration with a missing TRACEMST table would cause an application error. This issue has been resolved. (Issue: GAIN-4868)
Updated index and search keywords for topics related to Command Line Parameters and Shortcuts for Automatic Functions. (Issue: GAIN-3063)
The file.xls.columncount, file.xls.lastcol, file.xls.lastrow, and file.xls.rowcount Python commands documentation has been updated to include the following: Best practice: do not use this command in a loop. Instead, set it to a local variable and use that variable in the loop.
The SPC Data Entry module did not load the DMS Data Entry tab of templates. This issue started in version 10.1 and has been resolved. (Issue: GAIN-4866)
In PC Collect, the Numeric Input does not advance to the correct next cell in some cases. This can happen if the TabDirection property is set to Down, the Subgroup size is greater than 1, the VerticalSize property is not set to Regular, and there is an OnChange script. This issue has been resolved. (Issue: GAIN-4768)
In GainSeeker Charts, drilling down into a Pareto chart will always group the next level by the Defect category. This issue has been resolved. (Issue: GAIN-4766)
In PC Collect, traceability lists on a sub-inspection may be blank if you load that sub-inspection a second time without closing the Inspection. This issue has been resolved. (Issue: GAIN-4765)
If the first action in GainSeeker Charts is to load a Dashboard with multiple retrievals, the Auxiliary traceability columns may not load. This could affect Data Tables and OEE statistics. This issue has been resolved. (Issue: GAIN-4771)