This describes the resolution of known issues and corrections to the Online User Guide.
Under certain conditions when excluding outliers, the value for "Maximum good subgroup" reported a larger number than the value for "Maximum subgroup". This issue has been resolved.
If excluding outliers with multiple data groups, and gates are used for zone violations, the mean used to evaluate outliers could be incorrect and cause outlier evaluation to report incorrect results. This issue has been resolved.
Several SPC statistics could be reported incorrectly if excluding outliers for a data set with a subgroup size of one. This issue has been resolved.
Users without rights to change notes could still change an existing note if they had the right to add data and notes. Now users with this combination of rights can only append to the existing note. This issue has been resolved.
Users were unable to edit DMS data if the data was stored with a higher time precision that is currently being shown. This issue has been resolved.
When editing a data record and deleting a value from traceability fields 7-48 or SPC data fields 9-72, sometimes the value was not actually deleted. This could happen on a SQL Server 2005 database, or when the Convert.db file contained the setting UseQry=1. This issue has been resolved.
On a MySQL database, attempts to change values in a database record (such as an SPC standard) were not always successful. GainSeeker now uses the same method on MySQL that it was already using on SQL Server 2005 and later to perform insert, update and delete operations, and this issue has been resolved.
The Online User Guide has been updated to note that the configuration setting for Set nonconforming units = number of defects affects the analysis of DMS data records that are stored with a number of Nonconforming Units that is different from the number of Defects.
The Online User Guide has been updated to include instructions for calculating color ID numbers that can be used with the DE_OPT 2, DE_OPT 3 and DE_OPT 4 commands.
The Online User Guide has been updated to reflect that the Pp and Ppk statistics are now calculated for data sets that exhibit non-normal distributions.
The Online User Guide has been updated to note that the Match case check box will not impact the list of values returned by the search if you are running GainSeeker on a database, table or column where the Collation is case-insensitive.
Using the DB_SET_VALUE and DB_STD_SQL "SPC*" commands to create SPC standards would set an incorrect value in the database field for the coding method. This issue has been resolved.
If you removed unused columns from the DDAT_AUX table in the current configuration, the DB_DATA_AUX_SQL or DB_INSERT commands were not aware of the missing columns and thus would not generate an SQL string that you could use. These commands will now automatically detect which traceability columns remain in the DDAT_AUX table and will adjust the SQL string accordingly.
Increasing the subgroup size during a data entry session could generate a Run-time error 9: "Subscript out of Range". This issue has been resolved.
Using the SET_NOTE command to set a note ending with a space could result in a message about not having rights to delete or save a changed note. This issue has been resolved.
When using the DMS_COUNTS command to enter DMS data, the program allowed users to enter data for more than 20 types of defects and then generated a Run-time error 9: "Subscript out of Range". This issue has been resolved.
In previous versions, GainSeeker would round data values to the number of Decimal places in the standard or process specification being used to enter the data before storing these rounded values in the database. GainSeeker now stores the data values as they were entered and will only round the data values when formatting them for display.
In previous versions, template commands such as CHT_DASH could crash if more than 100 .jpg files existed in the destination folder. These commands could also crash if these .jpg files were created and deleted in the same template These issues have been resolved.
When running a Timed Session with a Display type of Minimized timer dialog, or when running a data entry template with the TIMER_DELAY command using a window_state of 1 (Minimized timer window), the default display properties for Windows XP or Vista sometimes makes it impossible to display all of the characters on the countdown timer. When displaying the timer on a minimized dialog, the timer now automatically strips off non-critical characters. For example: a time of 09:30:21 will now display as "9:30:21"; a time of 00:14:29 will now display as "14:29"; a time of 00:3:12 will display as "3:12"; and a time of 00:00:09 will display as "9".
When using custom dates to display records in the SPC Database Monitor module, charts that were launched from this module sometimes used an incorrect date range. This issue has been resolved.
When designing a Statistical Filter dashboard: if you choose All Data for your statistical filter, the color settings for this dashboard will now be ignored.
When editing a Real-time Failure dashboard, the dialog displayed the high date before the low date. This issue has been resolved.
When using the Desktop menu to send dashboards to HTML, some image files were placed in the wrong folder if the Cms.ini setting html_location= pointed to a folder other than the default for this setting. This issue has been resolved.
On a SQL Server database, opening a Real-time Failure dashboard could sometimes generate a "Cursor not declared" database error when one of the periods on that dashboard was "Last n records". This issue has been resolved.
When creating a new retrieval for a KPI gage, the default date period was always "Today to default low" - even if the default date period for DMS Charts and Reports or SPC Charts and Reports was configured differently. The default date period for a new DMS retrieval now comes from the configuration setting for the default date period for DMS Charts and Reports, and the default date period for a new SPC retrieval now comes from the configuration setting for the default date period for SPC Charts and Reports.
Using Prompt for changes for Part Number or Process would not work correctly when more than one part number or process was involved. This issue has been resolved.
Statistical Filter dashboards always reported 'NA' for Upper and Lower specification limits when the dashboard rows were defined by one of the Short Run traceability fields. This issue has been resolved.
The help topic on creating a shortcut to automatically open a desktop and save it as XML was updated to mention that the ability to specify the name and location of the resulting XML file is only available when the Server Edition is installed.
DMS drill-down data table allowed users to edit instead of view notes, and then reported an error. This issue has been resolved.
In some cases, the list of DMS standards was automatically filled even though the configuration was set to not automatically fill the list. This issue has been resolved.
On the dialog that displays statistics list formats, the caption for the "Save as default" check box was incorrect. This issue has been resolved.
When opening a desktop that did not include a setting for non-symmetrical control limits because the desktop had been created by a previous version of GainSeeker, GainSeeker automatically analyzed the data as if this setting were set to "false" instead of using the default setting from the current configuration. This issue has been resolved.
If a user displayed the Control Limit Legend for a control chart where no data groups were present, clicking the Zoom button would generate a Run-time error 5: "Invalid procedure call or argument". This issue has been resolved.
On step 3 of the Variation Wizard, selecting multiple items would generate a Run-time error 91: "Object variable or With Block variable not set". This issue has been resolved.
When a Short Run chart was displayed, GainSeeker did not correctly search for the relevant process specification when the user clicked the Setup menu and chose Current Value. This issue has been resolved.
The Store Gates screen would not allow a range gate to be set below 0, even though this is the default lower control limit for Short Run charts using the Standardized coding method. This issue has been resolved.
When a Short Run control chart was displayed, the user was not able to remove control limits from the range chart. This issue has been resolved.
On a Control and Bar chart, double-clicking a point on the X-bar portion of the control chart would not generate the Data Table. This issue has been resolved.
On Template Wizard Step 5, if the user changed a cell type from Keyboard to Formula and then supersized this dialog, it was possible for this cell to revert back to a Keyboard cell. This issue has been resolved.
On Template Wizard Step 5, clicking Find and then clicking Variables now lists MyNVars, MySVars, MyNArrs and MySArrs in alphabetical order. This makes it much easier to find a specific entry in the list.
The File Import Wizard and Database Integration Wizard have been updated to use the DB_INSERT command to store DMS data, instead of the more complicated template code that was being used in the "DMS Save" column.
Step 2 of the Database Integration Wizard has been updated so that a table name that contains (but does not equal) a reserved word will not be erroneously flagged as a reserved word.
The help topics for several commands have been updated to reflect the correct return value (–999 instead of 999) when the requested setting does not exist. These commands include: UPPERSPEC, UPPERGATE, UPPERCL, SUBGROUPSIZE, NOMINALSPEC, LOWERGATE, NOMINALGATE, NUMDEC, LOWERCL, LOWERSPEC, LOWERIND and UPPERIND.
The help topics for the CHT_DASH, CHT_DMS and CHT_SPC commands have been updated to note that if the charting modules used by these commands are already open on the workstation, executing these commands will close the associated charting module.
These topics have also been updated to note that if the focus does not returns to the SPC Data Entry module after executing this command, you can use the formula PBUFF : CLOSE_PBUFF to return the focus to the SPC Data Entry module.
The help topic for the SETCELL command has been updated to note that if you are setting the value of a cell in the Event, Cause or Action Taken column, your template must visit the cell after SETCELL has made the change.
The help topic for the Document tab has been updated to note that newer versions of Microsoft Office and document viewers (2003 and later) can no longer display an Office document directly on the document tab of a data entry template, even using the HTML redirect.
When setting file paths, previous versions of GainSeeker did not allow you to select a file path that contains a space. Now GainSeeker will try to detect the equivalent "short name" file path (which does not contain spaces) from the file system. If detected, GainSeeker will paste this "short name" file path onto the Edit File Path screen. Otherwise, you will need to enter a different file path which does not contain a space.
The following settings from Cms.ini have been moved to Settings.hsi:
data_tablespace=
index_tablespace=
query_timeout=
audittrl_table
The following settings from Cms.ini have been moved to Redirect.hsi:
physid=
user_name=
user_last=
Also, the html_res= setting has been moved from Cms.ini to the system-wide settings for Chart picture size.
The computer_name= and reqnetid= settings from Convert.db have been moved to Settings.hsi.
The following settings from Convert.db have been moved to system-wide settings:
audit_uc=
notify_days=
notify_date=
email_to=
email_subject=
email_name=
email_pw=
email_uc=