SQCpack release 6.5.13 SQCpack release 6.0.38 SQCpack release 5.5.92 SQCpack release 5.5.86 SQCpack release 5.5.79 SQCpack release 5.0.111 SQCpack release 5.0.104 SQCpack release 5.0.100 SQCpack release 5.0.82 SQCpack release 4.6.139 SQCpack release 4.6.136

SQCpack release 4.6.133 SQCpack release 4.6.118 SQCpack release 4.6.113 SQCpack release 4.6.112 SQCpack release 4.6.103 SQCpack release 4.6.99 SQCpack release 4.6.86 SQCpack release 4.6.76 SQCpack release 4.6.74 SQCpack release 4.6.67 SQCpack release 4.6.55

These changes and corrections were made after the 6.0.38 release and are contained in the 6.5.13 release (release date March 3, 2009)

• An update was made when saving SQCpack charts as CRF files.

• An issue with the out-of-control classifications has been corrected.

• In rare cases real-time charting locked up.

• An update was made to reference charts and reporting.

• An update has been applied for opening the data editor on a 64bit Vista PC.

• A reporting issue has been corrected.

• An issue in the reporting feature dealing with columns derived from calculated formulas has been corrected.

These changes and corrections were made after the 5.5.92 release and are contained in the 6.0.38 release (release date July 25, 2008)

• Updates were made to the OOC summary to respect the “Last N” setting.

• An error was corrected when you select Setup, Default Histogram, Data Selection.

• An error was corrected in real time charting when inputting data from a device.

• An update was made to the file/folder path code for automatic backups.

• In rare cases U-charts with multipliers displayed incorrectly.

• Updates were made to correct a rounding issue with values in the data grid above the chart.

• An error was corrected when data selection is set to Last N for right clicking and selecting “View subgroup information”.

• An error was corrected when entering data from PORTspy to SQCpack.

• Updated the error message a user who has only access to the real-time editor receives when they try to double-click on a group.

• In rare cases an error occurred when clicking the “Charts/limits” tab, select a chart, click the “Display selected chart” button on the toolbar, close the chart and then click the same button.

• An error was corrected for adding an annotation to a control chart when the “Connect X to the data value” is checked and the display is set to last “N”.

• An error occurred when selecting data points or group of data points when using a filtered date range.

• An error was corrected when trying to remove, edit or delete control limits on charts set to display Last N.

• Updates were made to the way control limits are calculated when data is added to the group.

• In rare cases adding additional data lines to multi-line charts caused an error.

• A correction was made to saving a chart as a CHARTrunner file.

• Adding a cause under real-time charting for np-chart causes an error.

• An update was made to the question mark on near the data entry format text box – on the measurement characteristic definition form.

• Updates were made to the Out-of-control summary.

• Updates were made to allow the chi-square setting on the histogram definition form to allow decimals to be entered.

• Updates were made to chart display when all of the data is the same and user defined Y-axis scaling is in use.

• The way SQCpack reports decimals in the reporting feature was updated.

• In rare cases setting Defects per “n” to 1000 would change the value to 0 after viewing and then editing the chart definition.

• In rare cases users with “read” rights were able to edit existing data in real-time charting.

• A preview reports error was corrected.

• The “send chart as email” feature was updated to use the image type of the chart being sent.

• In rare cases charts displayed during a chart review displayed incorrectly.

• Updates were made to the reporting feature in regards to using filters with grouping.

• In rare cases the OOC summary did not match the chart in a workspace.

• In rare cases choosing “auto-format columns” in the data entry screen erased all entries for all subgroups.

These changes and corrections were made after the 5.5.86 release and are contained in the 5.5.92 release (release date January 2, 2007)

• Highlighting subgroups error has been corrected.

• In rare cases annotation orientation was not saving correctly.

• Real-time charting produced an error when opening if it was setup to use limits and no limits were active.

• Real-time charting was not enforcing max/min allowable entries correctly.

• An error occurred when displaying control charts.

• The CPK (sigma shift) check box was defaulted to checked with no value entered.

• In real-time charting using different ooc styles produced an error for short run charts.

These changes and corrections were made after the 5.5.79 release and are contained in the 5.5.86 release (release date November 30, 2006)

• Hotkeys were added for each option on the data selection form.

• An error was corrected where Pareto charts would show a value of one for categories with a zero count.

• A memory leak error in real time charting was corrected.

• Labeling an x-axis with a DateTime and using the “group-by minutes” option did not always work properly.

• In some cases spec line were not being displayed correctly.

• An error was corrected that caused SQCpack to crash when entering data into a child chart of a multi-chart when the multi-chart is displayed with a refresh interval.

• In some cases multi-charts displayed with refresh intervals would display incorrectly.

• SQCpack was not correctly storing control limits marked as the active set of limits.

• When calculating limits on data ordered by a Date identifier SQCpack could generated an error.

• Spec lines entered as extra lines did not always display and get labeled correctly.

These changes and corrections were made after the 5.0.111 release and are contained in the 5.5.79 release (release date October 23, 2006)

• In rare cases only the label for the LSL (lower specification line) was displayed.

• Short-cut (hotkeys) were added for each of the options on the data selection form.

• Printing or exporting group data would not print or export the calculated characteristic data if data selection was changed from ‘All’ to ‘Last 15’ (last custom range).

• Editing the font of a title would cause other titles to not display.

• In some cases an error occurred when adding a new category to Pareto groups when the Misc. tab in the Group Modify has “Auto Fill Categories = None”.

• In rare cases the selection rectangle becomes distorted when highlighting a set of subgroups.

• Charts printed with incorrect margin sizes.

• In some cases the first data point of and out-of-control test appeared as a normal data point instead of a hollow square.

• Email alarms were not getting sent out for P-charts.

• In some cases user edits to the label column for the data grid were not respected when drawing the chart.

• Changes were not saved when only changing the “max length” field on the form for editing a multi-line chart definition.

• A run time error occurred when control limits were applied to a chart with a calculated characteristic.

• In some cases editing or creating a histogram style produced an error when trying to save.

These changes and corrections were made after the 5.0.104 release and are contained in the 5.0.111 release (release date May 17, 2006)

• In rare cases using the data entry screen while a chart was displayed would not update the chart.

• In some cases the lower spec line label would move from the lower spec line.

• SQCpack now correctly displays the date 1/1/1900.

• In rare cases color sigma zones did not display when selected.

• In rare cases the data entry grid above the chart displayed when turned off.

These changes and corrections were made after the 5.0.100 release and are contained in the 5.0.104 release (release date February 2, 2006)

• Using the default control chart icon vs. drawing the chart from the charts/limits tab would sometimes apply control limits inconsistently.

• In some cases selecting View Subgroup Info always displayed information for the last subgroup regardless of which subgroup was selected (on the chart.)

• The error message was improved when SQCpack encounters an error trying to open a database.

• On charts with multiple control limits, in some cases SQCpack was not applying the limits to the correct starting and ending subgroups.

These changes and corrections were made after the 5.0.82 release and are contained in the 5.0.100 release (release date October 10, 2005)

• When adding a new subgroup during real-time charting certain groups would cause a type mismatch error to be reported.

• Displaying charts, printing data, and exporting data, from the main form could cause a slow memory leak.

• In real-time charting, the F12 key (next subgroup) was implementing the new subgroup function.

• Displaying any second chart from the data entry form could cause an object variable or with block not set – error.

• In real-time charting, when the chart is set to 10 subgroups wide, when you first enter data and get to the tenth subgroup, the chart width could automatically get changed to 3 or 4 subgroups.

• In a Report that was grouping by a date identifier – on months – would not create the correct groupings when any of the date identifiers was missing.

• Certain Pareto charts that used a Date identifier for group-by would give an error message saying Identifier not found.

• Groups with a Date-Time identifier sometimes incorrectly display 12/31/1899 when the user presses ENTER to automatically enter the date.

• Exporting a report to Excel or HTML could cause an incorrect file not found error message.

• When doing a report with date grouping by week and using either a calculated or a count characteristic, you could get an object variable or with block not set error.

• For some groups containing np count characteristics, the data grid above a real-time control chart did not update as new data was added by the user.

• Reports that contained a large number of report items, where the database contains a large number of groups could eventually stop working and display an out-of-memory error.

• When doing block delete in the data entry form that removed rows up to the end of the subgroup records, an error message saying Invalid property array index could be displayed.

• Control charts can get saved in such as state that they always display a blank data grid above the chart – no matter how the chart definition was setup. This sometimes occurred after changing global settings under Setup/Default control chart.

• Charts that used a numeric id for the x-axis label could sometimes cause SQCpack to exit ungracefully – with no error message.

• When clicking on a control chart to highlight a subgroup, if the chart used a filter, sometimes the highlight would appear on the wrong subgroup.

• A group that contained a Pareto characteristic – when opened for real-time charting – did not always perform the out-of-control actions properly for the “total” of the Pareto counts.

• When all or many of the options are checked for building the out-of-control message that would be sent in real-time charting, the message can look pretty messy. Improvements were made in formatting/spacing this message.

• When using an np-chart in real-time charting, if you enter a count that is larger than number inspected, you can get into an error message loop that is difficult to get out of.

• When using a group that contains more than one characteristic – in real-time charting, sometimes the out-of-control actions will not occur for the second characteristic. This was first noticed when the second characteristic was an np-chart; however, it can also happen for measurements.

• This error was only seen in an internal (not-released) version of SQCpack. Some groups with u-charts or p-charts showed an extra column in the data entry grid and also give an error on the way into the editor: Invalid property array index.

• Use a group with one date identifier and one np-characteristic. Add one subgroup using the regular data editor. When you open this group for real-time charting, and then try to enter a NEW subgroup using (F3-New), you can get this error: Invalid procedure call or argument.

• Legends on newly created Pareto (pie) charts did not always contain all of the category names.

• Some email systems require authentication via user name and password. Support was added to allow SQCpack to authenticate against the users email system. Name and password were added under Setup/Preferences/Email

• In some groups, pressing TAB after entering a measurement value in the regular editor could cause this error message to appear: frmGroupDataEntry.ValidateEntry (23)] Type mismatch.

• The /cp command line argument (to print a chart) did not work. It displayed a no columns defined error.

• A calculated characteristic that does division could lockup up SQCpack if the user entered values forcing a divide by zero.

• Copy choice list was not working.

• On SQCpack databases that are password protected, the user is prompted twice for the password.

• This error was only seen in an internal (not-released) version of SQCpack. Creating a group with one Pareto characteristic would display this error message:

  [Application.CreateNewChart] Unable to get limit

• After adding several new subgroups during real-time charting – when using a group with multiple characteristics, occasionally the chart will display large red squares (like the OOC marker).

• In some groups containing Pareto characteristics, if multiple categories start with the same word, they may be combined into a single bar on the Pareto chart. For example, Coffee, instant and Coffee, brewed might be combined into one Coffee category.

• For certain short-run spc charts, SQCpack was mistakenly treating missing data as zero.

• With some complex groups (groups containing multiple characteristics and mixed characteristic types) real-time charting chart updates can become inconsistent after several subgroups are added.

• When creating a new control chart – for a characteristic already has multiple sets of control limits created – the existing control limits do not show up on the chart definition form. After you save – then modify the chart – the limits do show up.

• When auditing/prompt for reason is enabled – some auditing events would prompt twice for the reason.

• During data entry, when using the Ctrl-D (duplicate from above) feature – a displayed chart would not update with the new data.

• Charts that filtered base on a Time or Date-Time identifier were not filtering correctly due to an invalid date of 12/30/1899 being used in the filter condition.

• Control charts that used a date identifier for order by would incorrectly put all temporary control limits at the save value.

• In real-time charting calculated characteristics did not always cause the chart to refresh when new data was added.

• When creating a multi-chart, selecting a chart from a password protected group could cause an error message endless loop problem.

• A group that is configured for displaying the real-time chart form in full screen lockout mode – could cause the following error – when opening the group for real-time charting:

  [frmRtChart.Process (55)] Form already displayed; can't show modally.

• Multi-line charts allow you to define up to 10 data lines - but only were only showing 4 data lines on any chart.

• The regular data editor will update any relevant charts that are displayed in other windows during data entry. Data that arrived from an RS-232 device was not updating the charts.

These changes and corrections were made after the 4.6.139 release and are contained in the 5.0.82 release (release date October 25, 2005)

• PORTspy 5.0 would not correctly read the groups from an SQCpack database.

• Trying to save a short-run Difference/MR chart with computed limits – could cause this error: Unable to save limit.

• Pasting data into the data entry form did not always do the right thing when running in a locale where the comma is used as a decimal. Other errors related to using the comma as a decimal were also corrected.

• Opening a Pareto group – which contains no data – for real-time charting – could cause the following error: frmRtChart.grdData_LeaveCell (7)] Object required or this error: Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.

• Data entry for short-run products required an extra “Enter” key to move to the next column. This was corrected.

• Modifying a group by deleting a short-run product could cause this error: Invalid procedure call or argument.

• A histogram which looks at many rows of data – where all or most of the values are missing – could cause SQCpack to lock up.

• Some histograms with mostly negative numbers could cause the following error: Meth ‘Draw’ of object _PQQC4 failed.

• The feature “View subgroup info” did not always show the correct data values for the selected subgroup. This typically happened when the chart was looking at filtered data.

• A real-time chart that is defined to warn on out-of-spec can produce this error: Object variable or with block not set. This can occur when the user closes the warning message form with the red x.

• Attributes charts that are refreshing from the regular data entry grid can cause the following error when trying to refresh: Object variable or with block not set.

• Added the feature that any visible chart – related to the current data entry session – will be refreshed as new data is entered. In effect, all charts are “real-time” charts.

• During Pareto data entry under real-time charting – we allowed the user to type into the total cell at the bottom of the Pareto categories grid. This could cause the following error: Not a valid object.

• Manually entering a date identifier in real-time charting could cause Type mismatch errors.

• Some control charts, which show out-of-spec points near the right side of the chart, incorrectly show the points as OK after a new row of data is added during regular data entry.

• Double clicking – to add a chart to a multi-chart definition – could cause the following error: Method or Property not available at this time.

• In some groups, adding one or more new rows of data could cause existing control limits to not show on the chart – despite being visible on the chart definition form.

• The new feature where all visible charts update with new data –was not working when the data came from an RS-232 port.

• In the data entry form, when the current cell is a calculated characteristic, the specifications did not show up in the status bar like they do for regular characteristics.

• For characteristics with only one specification – SQCpack was disabling the option for testing against specifications on the chart definition tab.

• Multi-line charts allow you to configure up to 10 data lines but were only showing a maximum of four on the chart.

• Opening an empty group for real-time charting – where the “view stats grid” option is turned on – could result in this error: Invalid procedure call or argument.

• If a global user database is deleted and SQCpack is setup to use this database – the next time you start SQCpack – it will prompt you for a database password. Now, an appropriate error message is displayed.

These changes and corrections were made after the 4.6.136 release and are contained in the 4.6.139 release (release date June 30, 2005)

• A problem was corrected which allowed you to enter new date/time identifiers but prevented you from making changes to existing date/time identifiers.

• Creating an identifier with an auto-increment formula of +1R will result in the following error message: Invalid auto increment formula. +1R means “plus one quarter” for a date identifier. This was corrected.

• In some situations, users with no modify privileges were able to delete subgroups from within the real-time charting module. This was corrected.

• In some configurations, inserting a new subgroup (between existing subgroups) in real-time charting can cause the software to hang. This was corrected.

• On the control limits form for p-charts and u-charts the limit values are shown with no decimal places – even though they are correct on the charts. This was corrected.

These changes and corrections were made after the 4.6.133 release and are contained in the 4.6.136 release (release date March 11, 2005)

• Real time charting was improved to respect the decimal places setting from the chart – when applied to the “statistics grid” on the right side of the form.

• The most recent build/release of SQCpack does not include a required component – vsflex8l.ocx. This prevents a user from collecting data from a RS-232 device. This was corrected.

• Recent fixes to pasting data into the data entry grid from the clipboard introduced new but different errors where “not enough” data gets pasted. This was fixed.

• Adding a new subgroup in real-time charting can end up changing the number of subgroups displayed on the real-time chart. This was corrected.

• A data point that falls exactly on a control limit – when the control limit is a value entered by the user – can be marked as out-of-control – even though it is not out-of-control. This floating point decimal precision error was corrected.

• SQCpack can hang when computing limits on a c-chart or other attributes control charts. This was corrected.

These changes and corrections were made after the 4.6.118 release and are contained in the 4.6.133 release (release date January 17, 2005)

• Pasting data from the clipboard into the data entry form can result in extra rows being pasted.

• When using a group with 2 or 3 measurement characteristics, in real-time charting, adding a new subgroup (F3) and then moving to another characteristic (F8) can cause the chart and data entry grid to get out of synch.

• Improvements were made that help @Cpk used as a chart title – report the same number from real-time charting as it does for the “regular” chart. Note that in many cases these will be different values because different subgroups are being used to compute the value.

• The preference for “number of subgroups to include” – under Setup/Preferences/Real-time charting – was not being respected. Related to this is problem where clicking on a subgroup (in the chart) in real-time charting – does not highlight the subgroup as it should.

• An error in reporting that prevented “export to Access” – was corrected.

• In real time charting, if the group has multiple identifiers, and one of the identifiers in the middle of the list is setup as “required” – during data entry if the operator does not enter this, they are prompted to enter a “different” identifier.

• During real-time charting, if an out-of-control action is defined to prompt the operator for a note or a cause – the user can get stuck in a loop where the note/cause form keeps coming up.

• In real-time charting, if the chart type is “run chart”, the following error message can be displayed: Error computing limits in UpdateChart. This was fixed.

• Only one user may open a group for data entry at any give time. An error was corrected which was allowing multiple users to open the same group (at the same time) for real-time charting.

• If real time charting is setup to send email on out-of-control conditions and the email is defined to include the database name, the email message does not contain the database name.

• When sending a test email message (from Setup/Preferences/Real-time charting) a different “from” address was used – than the “from” address that was used during real-time charting. This was made consistent.

• When using an RS-232 data device for data entry some readings can get truncated.

• When using an RS-232 data device for data entry – in locales where the comma acts as the decimal separator, readings from the device are not handled properly. This was fixed.

• A user with “view only” privileges is sometimes allowed to edit the causes and notes associated with subgroups. This was fixed.

• Real time charting was improved when identifiers are modified on existing subgroups. Sometimes the changes were not being applied to the correct subgroup.

• When entering the very first subgroup into real-time charting, when you have a required identifier, can result in the following misleading warning message:
  A required identifier was not entered.

• In some configurations, real-time charting is not sending email – even though a “test” email will work. If the email system was setup by one users – and then a “different” user logged into the workstation – SQCpack would not find the correct email setup information. This was fixed.

• An error was corrected that would not allow the saving of a report to HTML.

• The data grid above the chart, for a run chart, when subgroup size is greater than one, is not always synchronized with the data plotted in the chart.

• Changes were made on the Pareto chart definition for to allow the user to not show the “totals count” above the Pareto chart.

• Column alignment was improved in reports that are shown in “transposed” mode.

These changes and corrections were made after the 4.6.113 release and are contained in the 4.6.118 release (release date September 1, 2004)

• A report that uses a filter (at the report level) based on an identifier that not all groups contain – will display a long confusing error message – ending with “Syntax error.” This condition is now detected and a friendly message explaining the situation is displayed.

• An individuals/moving range chart – where the number of subgroups in the moving range is more than 2, can display incorrect information – when you select “View subgroup information” – from a highlighted subgroup on a control chart. This was fixed.

• When a chart is saved as an EMF (image file), if it contains angled text, say on the x-axis labels, the angle is not correct. This was corrected.

• Clicking around in the plot area of a Cusum control chart can cause the v-mask to be displayed “off” the data line. This was resolved.

• The ability of histograms to handle large datasets – without generating an error message – was improved. The error message was “Method ~ of Object ~ failed.”

• The following error could be encountered when using File/Utilities/Test and repair database:
  [frmDataIntegrityTests.TestSubgroupTableForMissingColumn]
  Item cannot be found in the collection corresponding to the requested name or ordinal.

• Improvements were made to how @Cpk works – when used as a chart title.

• A choice list added while creating a new group is not visible (on the main form) until you exit and re-enter SQCpack. This was fixed.

• When labeling specifications lines with name and value – in either control charts or histograms – some values get rounded inappropriately. For example, an USL of 1.234, might show up on the chart as 1.

• Added an option on the Pareto chart definition form, to force bar labels to be outside the Pareto bar.

• Displaying a histogram or a the combination chart – from the data entry form – can result in a long error message that ends with:
  Error preparing chart
  No value given for one or more required parameters
  This is due to an invalid column name being saved as the “order by.” This has been fixed.

• A new test was added to the File/Utilities/Test and repair database option. The test looks for invalid data selection filters that can cause the following error on some charts:
  No value given for one or more required parameters.

These changes and corrections were made after the 4.6.112 release and are contained in the 4.6.113 release (release date June 30, 2004)

• Selecting “Next subgroup” in real time charting can cause the following error:
  [frmRtChart.CanEditSubgroup (3)]
  Either BOF or EOF is True, or the current record has been deleted.
  Requested operation requires a current record.
  This was fixed.

• An error was fixed where certain Pareto charts would display the message:
  Invalid Parameter

• Adding or editing causes and notes in the data entry form can cause duplicate notes and causes to show up. This was corrected and only shipped in the product for a two week period in June of 2004.

• On the Pareto chart definition form, improvements were made to how we decide if certain options are enabled. In some cases, the cumulative line was not enabled when it should have been.

These changes and corrections were made after the 4.6.103 release and are contained in the 4.6.112 release (release date June 11, 2004)

• Opening a group with Pareto data for real-time charting can cause the following errors:
  [frmRtChart.grdData_AfterRowColChange] Object required
  [frmRtChart.BeforeDataEdit] Object required

• When you open a group for real time charting, which has a characteristic containing a data entry format such as 1.###, and you also have “auto-copy” identifiers in the group, pressing the Esc key – as soon as you arrive on the real-time chart form – can cause the chart to refresh with incorrect information. Additionally, record locking errors may be displayed.

• When defining a report template, column width could not be entered as a percent of the page; instead, this was interpreted as pixels. This caused unexpected column widths to show up in the report.

• Some reports incorrectly label the page with 1 of 4 when there are actually more pages.

• When trying to create an X-bar/Range “auto-chart,” using data in the clipboard, the following error is displayed:
  [PqChartMaker.PrepVarControlChart (23)]
  Object variable or With block variable not set
  Also, when using the “auto-chart” feature, Pareto chart is not an option in all cases when it should be. Finally, two columns of attributes data in the clipboard can cause “auto-chart” to produce and error like this:
  [PqChartMaker.PrepAtrControlChart (21)]
  Object variable or With block variable not set

• In real-time charting, just pressing the Enter key to cycle through many subgroups can eventually cause an error like this:
  [PqRtChartMaker.GetChartsCharFormatLength (5)]
  Object doesn't support this property or method.
  Other errors that might show up in this situation:
  Invalid use of Null
  [frmRtChart.DeleteCurSg (15)] [PqOio.SubgroupDelete (28)]
  Could not update; currently locked.

• A report that contains a report item – for which no data has yet been entered – may display an error message like this:
  [SqcReportMaker.SortReport (3)] Invalid property array index

• In real-time charting, editing the identifiers for one subgroup and then moving to another subgroup via the “previous” or “next” button – could cause the original identifier changes to be lost.

• Changes were made to how the data grid above a control chart is edited and saved. In case, the statistics options did not get applied to the chart even though they were selected.

• When saving a histogram as a clip chart, you might encounter the following error:
  [frmMain.SaveChartAsCrFile (39)] [PQCrDef.GetChartRecordSet1 (20)]
  Query must have at least one destination field.

• A new menu selection was added. Help/PQ Systems on the Web/View product tutorial.

• Improvements were made in Reporting, where a numeric identifier is used to do grouping on a per group basis.

• Under File/Utilities options were added for testing and repairing databases.

• Changes were made to how Reporting lays out columns on large multi-page reports. In some cases too much space was being wasted on each page.

• A new reporting option was added to not include groups which contain no records. This allows a report to be defined for All groups/All characteristics – and still work properly if some of the groups have no data.

• Problems were corrected where secondary sort order did not work properly for reports.

• An error was fixed that prevented a “copy” of any “default” charts – from ever being deleted.

• In the data entry form, clicking on the “Procedure” button, could put the editor into a state where the procedure window would keep coming up whenever you changed columns. This was corrected.

• Deleting multiple sets of control limits from a chart that is displayed – and then clicking on the default control chart button – could cause the following error:
  [frmGroupDataEntry.DisplayDefaultChart (16)]
  Object doesn't support this property or method

• Selecting “Setup/Default Pareto chart” resulted in this error message:
  [frmMain.EditDefaultCharts (16)] [SqcChart.Edit (30)] [SqcChart.ParetoToForm (44)] Object variable or With block variable not set
  This was corrected.

• The option for reports to include “number of data points” was improved.

These changes and corrections were made after the 4.6.99 release and are contained in the 4.6.103 release (release date March 19, 2004)

• This error message:
  [frmMain.AddDBInfoToTree] Key is not unique in collection,
  is displayed when you open your first database AFTER setting up a new global user database.

• Generating some reports – based on measurement data – can product the following error message: Unable to print report,
  [SqcReport.PrintReport] [SqcReportMaker.SetupReferenceCharts]
  Error setting measurement data [PQDataMgr.ParallelData (102)] Invalid Field name: ID7

• Reports which reference a Cusum control chart can generate the following error message:
  Unable to print report,
  [SqcReport.PrintReport] [SqcReportMaker.CountSubgroupsOOC] Unknown

• Some report templates can cause the following error when a report is generated:
  Unable to print report,
  [SqcReport.PrintReport] [SqcReportMaker.CalculatePages] Division by zero

• A maintenance reminder scheme was implemented. 365 days after the initial install a reminder message about maintenance will be displayed – just a few times.

These changes and corrections were made after the 4.6.86 release and are contained in the 4.6.99 release (release date February 24, 2004)

• Added @OOC as a new chart title option.

• @CPK as a chart statistic title did not work in real-time charts.

• Corrected problems when calculated characteristics were not shown in the print preview and data export to text file options.

• Fixed a "memory leak" which sometimes caused SQCpack to stay resident in the memory when the program was exited.

• Pressing Enter added two rows of data when the "next direction" was set to down and the date identifier was automatically incremented.

• Modified SQCpack so that the default control chart (required) cannot be deleted with the Delete key.

• Max, Min, and Increment values sometimes disappear from the CUSUM chart definition after a chart with user scaling was edited.

• When changing from a Pareto bar chart to pie chart, the software automatically selected the multi-chart option and disabled the check box so it could not be unchecked.

• "Invalid user entered Y-axis scaling" could occur when a user entered negative numbers.

• Added .PNG as a new option for Multi-chart images.

• In some cases SQCpack would exit when a user clicked on F3-New in the real-time chart.

• "[SqcImport.WriteParetoData (15)] Item cannot be found in the collection corresponding to the requested name or ordinal" could occur when importing data into Pareto groups.

• "Method ~ of object ~ failed" could occur when user-defined cell definitions or specifications were missing.

These changes and corrections were made after the 4.6.76 release and are contained in the 4.6.86 release (release date December 5, 2003)

• On a double chart (for example, X-bar and Range), data points that were out-of-control on both charts were counted twice on SQCpack reports.

• "[frmChartDisplay.EditLimitProc (9)] Unexpected condition" which occurred in some situations when attempting to edit one of multiple control limits on a chart. This occurred due to an unexpected space at the end of the control limit name.

• SQCpack now prevents multiple groups with the same name in the same database.

• Adjusted the print preview and export data functions to include calculated characteristics.

• Improved handling of commas used as decimals.

• Enhanced printing fill patterns.

• Modifying a group could cause reverting to an older set of control limits as active.

• Improved handling of missing data in histograms.

These changes and corrections were made after the 4.6.74 release and are contained in the 4.6.76 release (release date October 13, 2003)

• Turning of the data markers on a Multi-line chart no longer turns the chart legend off.

• Corrected the real-time charting function that plotted small values, such as 0.003 as zero until the chart was refreshed.

• Improved what occurs when a group was modified to change a text identifier containing dates to a date identifier. The modification sometimes changed the data order.

• "A field is too small to paste data" which occurred when adding a characteristic to a group that had already been modified was corrected.

• "[frmMain.ModifyGroupProc] Object variable or With block variable not set" could occur if the view toolbar option was not selected and a group was modified.

• Adding a characteristic to a group caused the causes and/or notes to disappear from existing data.

• Improved the printer selection form.

• Enhanced the Test and repair database function.

• Improved reports to better handle those with several groups and each with many subgroups.

• Adjusted the Lock identifiers option so that users can scroll through data columns even when there are more identifier columns than can fit on one screen.

These changes and corrections were made after the 4.6.67 release and are contained in the 4.6.74 release (release date July 25, 2003)

• Reports with filters similar to @ThisMonth-1 do not include the data expected.

• Column headings in the report templates are not applied correctly across multiple pages.

• Overwriting a Pareto category name with a number resulted in an error "[frmGroupDataEntry.SaveParetoData (31)] Object variable" or "With block variable not set."

• "[frmMain.PerformDatabaseIntegrityTests (25)] [Application.CompactRepairDB (14)] Object variable" or "With block variable not set" occurred when running the Test and Repair utility.

• "[frmMain.CopyGroupProc] [Application.CopyGroup] [PqOio.CopyCausesNoteTable] Object variable" or "With block variable not set" could occur while copying an existing group with data.

• "[frmGroupDataEntry.Process (5)] [AppEnv.CreatePqObject (67)] ActiveX component can't create object" occurred during startup.

• Real-time data entry could save 0 as a null value instead of 0.

• Improved the e-mail controls and added support for the Mercury e-mail system.

These changes and corrections were made after the 4.6.55 release and are contained in the 4.6.67 release (release date May 21, 2003)

• Added two new title codes@ESIMGAR and @ESIGMAS to allow the user to select estimated sigma based on the range or estimated sigma based on the sigma.

• @SIGMA still displays sigma of the individual values.

• Improved handling of p-chart temporary limits.

• In some cases the number of digits after a decimal in control limits calculated through the chart display was incorrect.

• Improved synchronization with MEASUREspy.

• Fixed an error that did not order multiple Pareto charts by date identifier.

• A message "[frmGroupDataEntry.DisplayChartProc]" could occur while processing the chart when dragging a group into a new database and copying the data.

• "[Application.ModifyGroupDefinition (89)] [PqOio.GroupSchemaSimpleDataTransfer (66)] Data type mismatch in criteria expression" occurred when modifying a group and changing a text identifier to a date identifier.

• Changed handling of groups added to reports so that groups are ordered alphabetically in the Add form.

• Change handling of numeric report columns to that when the report is saved to an Excel file, the columns are saved as numeric rather than text.

• "[SqcGroupDataSource.OpenTable (15)] [PqOio.GetGroupRecordset (43)] Syntax error in FROM clause." "[frmEditorSubgroupData.ConfigGrid (16)] Invalid property array index [frmEditorSubgroupData.Process (6)] Invalid property array index." These messages occurred when opening the Subgroup editor in a chart that was drawn through the main tree without first selecting a group.

• Enhanced to track the size, location, and window state of the Report preview window.

• "[SqcChart.ChartFormEvent (25)] [PqOio.PutChartAnnotation (11)] The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data." This error occurred on converted databases when a chart was saved with two or more new annotations.

• Improved conversions from SQCpack for Windows.

• Multi-chart sometimes shows temporary limits even though the source chart used saved limits and the saved limits displayed correctly on the screen.

• Sometimes the control limits disappear when switching the chart type from X-MR to Individuals.

• Improved the print Chart workspace function.

• Deleting an annotation was only temporary. When the chart was redrawn, the annotation returned.

• Improved real-time charting so that the cursor is automatically set in the first measurement field if the identifiers are automatically incremented.

These changes and corrections were made after the 4.6.46 release and are contained in the 4.6.55 release (release date March 21, 2003)

• Default width of chart in subgroups now sets to start at the right. The default used to start at the left.

• Chi square did not always display correctly in reports.

• Text outside of Pareto charts was missing or misplaced.

• Reports were not calling on the histogram $Report to get the proper settings.

• Deleting a characteristic from a group with multiple characteristics, where multiple sets of limits were created for each characteristic, deleted control limits valid of the remaining characteristics.

• Title codes @CoName, @DBP, @DB were made to work as title substitutions on SQCpack reports.

• Changing the Cusum chart's sigma vs value setting did not save the change. Also fixed an error that allowed the characteristic's target specification to override the target specification specified for the Cusum chart.