This error occurs when the MS Vista/7/8 installation does not allow access to the Program Files folder. To correct this problem, re-install using the Run as Administrator options as described in Installation Instructions.

Return to top

Error 75: Error in StartVista. Vista error 302: Path/File access error

This error occurs when the user does not have write access to the SPC Explorer database. If the database was installed to the Program Files folder on a Windows Vista/7/8 computer, then the database must be moved to a folder outside the Program Files folder. See Installation Instructions.

Return to top

Run As Administrator option not available during installation

If the Run As Administrator option is not available in the right mouse menu when you select the setup.exe file that was extracted from the download, then your Secondary Logon service has been disabled in Windows. Navigate to the Services (Local) list (e.g. search on "services" from Control Panel), then double-click on the Secondary Logon item. Change the Startup Type from Disabled to Manual, then click the OK button to save the change and close the dialog box.

Return to top

Unable to open SPC software when using MS Access database, OR, Unable to open Microsoft Excel files for import or link

The Microsoft Data Access Components are required when used in conjunction with MS Access database, or when linking or importing data from MS Excel. Under normal circumstances, MDAC will already be installed on Windows 7, 8 and 10. However if this component is not installed, out-of-date, corrupt, or has been removed, SPC-PC IV Explorer will be unable to open an Access database. A message box will inform the user that it needs to be installed when launching the application. Version 2.8 or greater is required. Download MDAC: http://www.microsoft.com/en-us/download/details.aspx?id=5793. In addition, the drivers for the newer XLSX format are NOT included in MDAC, so to import or link Excel xlsx files users may need to install the 2010 Access Engine (Install the 32-bit version regardless of operating system type): https://www.microsoft.com/en-us/download/details.aspx?id=13255.

Return to top

Error in clsConnection.GetDatabaseConnection: Named Pipes Provider Could not open a connection to SQL Server

See installation instructions for SQL configuration settings.

Return to top

Run Time Error Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

This error can occur if the machine that gets this error has the database opened using the SQLServer 2000 or Earlier option instead of the SQLServer 2005 or Later option. This can be determined by viewing the Database Type field in the Explorer view's Database Properties window (select the Database label at the top of the Explorer view's left pane and the Database Properties window will open in the right pane). The database option will be specified on this line. For example: SQL Server 12.0.2269.0 - RTM (Enterprise Edition (64-bit)) (2005+). To correct the error, click the Open Database button in the Database Properties window, then use the Microsoft SQL Server 2005 or Later option to link to the database on the SQL Server.

Return to top

How to turn on detailed error messages to troubleshoot an issue

Open the Database Properties window (select the Database label from the top of the left pane in the main Explorer view), then double-click om the words (i.e. field label) Application Version. This opens a Troubleshoot dialog box, where you can turn on Show Detailed Error Messages.

Return to top

This error occurs if the referenced file was not registered during the installation, which is usually addressed by using Run As Administrator during installation, after all other software has been closed and the system rebooted. If the installation was not performed in that manner, uninstall and reinstall the software. (See Installation Instructions). If Run As Administrator was used during installation, then manually register the file using regsvr32 with an elevated command prompt. This is accomplished as follows, on the machine with the issue:

Type “Command Prompt” (without the quotes) into the Windows search bar.
Windows will return the Command Prompt desktop app as a possible result. Select this option, then the Run As Administrator option from the right mouse menu.
Select Yes to allow changes to the computer.
Type (without the quotes) "cd C:\Windows\system32" for a 32-bit machine, or "cd C:\Windows\SysWOW64" for a 64-bit machine, then press the Enter key. The Command Prompt utility will return the name of the current directory, which should match the directory entered in the last command.
Type "regsvr32 filename.ext" (without the quotes), then click the Enter key, where filename.ext is the filename and extension of the file with the registration error noted in the error message. For example: regsvr32 mscomct2.ocx
Windows should return a message that the file was successfully registered.

Return to top

You will get this error when a required driver is not installed. For example, if you are trying to link to an MS Excel file, you need to have the appropriate Excel driver installed on the machine that is connecting to the data source. When using the SPCserver service for alerting of external data, the server must have the necessary driver installed so it can open the data source for analysis.

Return to top

Can I see a quick overview of the software, or get a more detailed view of the software?

See the Quick Overview video to get started. We can also provide a personal demonstration of the software for you and your colleagues via a web meeting, which typically last 45 minutes to an hour. These web meetings may be scheduled through the Contact Sales button .

Return to top

How do I link a characteristic to an external data source?

For data in MS Excel, the easiest method is to use the File Open toolbar button in the Explorer view. Once you've opened the data in the SPC spreadsheet, use the right mouse option to either Link to Characteristic (if you want the SPC software to continually monitor the Excel file for new data) or the Import to Characteristic option (to bring the data into the SPC database as it is currently in the Excel file, with new data directly added to the SPC database). See also ToLinkCharacteristicToDataSource.pdf for more complete details.

Return to top

Can you add data (such as Manufacturing Order number, Serial Number, etc.) via a barcode reader to the Traceability Fields?

If the barcode reader is a keyboard emulation type reader, then just put your cursor into the field then scan from the bar code.

Return to top

How do you delete Work Sets, Parts, and Characteristics?

Prior to v3.1, Work Sets, Parts and/or Characteristics that were no longer needed could be made Inactive. Version 3.0 provides the ability to limit the views to only those records based on specified criteria (such as Active Only). Version 3.1 (and thereafter) allows deleting of Work Sets, Parts, and Characteristics, as well as Gages and ODBC Import definitions.

Return to top

If a Characteristic is Inactive, why is it shown in a Work Set view? You shouldn't be able to collect data on it.

It was designed this way to allow on-line users the ability to view a characteristic without collecting data for it. If you don't want to see the characteristic in the Workset, you should use the Remove button in the Define Workset dialog to remove the characteristic from the Workset. Note also that Auto Advance feature will bypass the Inactive characteristic, and that data cannot be collected for the Inactive Characteristic.

Return to top

How do the new server-side services work for alerting, emails, PC-DMIS imports and maintaining a centralized database?

The following settings within SPC-PC IV Explorer are useful, or in some cases necessary, to effectively use the SPCServer service for MS Windows.

A database name may be specified in the General tab of the Preferences dialog box (from the Tools menu). This database name is particularly useful for the data upload feature. Specify a useful name to differentiate between data from each of the local databases (i.e. each plant or local facility) within the centralized database.
The Scheduled Tasks dialog box (from the Tools menu) is used to enable (turn on) or disable (turn off) each of the following functions within SPC-PC IV Explorer. Each function-specific tab also offers Days / Hours / Minutes / Seconds boxes to specify the frequency at which the local database will be queried for each function (described at top of this page).

The query frequency in the Alerting tab refers to the query of external (linked) data, whose alerting properties are defined within a Process Monitor analysis definition.
The Email tab defines the frequency at which emails are sent from an email server. The email server is defined in the SMTP/POP3 tab of the Preferences dialog box (Tools menu). The emails include alerting emails (defined for characteristics), as well as security emails (defined in the Access Control tab of the Preferences dialog box, when the CFR option is purchased.
The Upload function queries the local database at the specified interval, then uploads new data to the specified centralized database (see QAWeb Service installation below).
The PC-DMIS tab is used to specify the files that will be queried (at the specified interval) for new data from the PC-DMIS device.

Return to top

The SPC software has suddenly stopped sending e-mails when alert conditions occur in the Work Set view or as defined in a Process Monitor chart in the Explorer view. What is the quickest way to resolve this issue?

There are two methods for sending alert emails. In the simpler method, the emails are sent directly from a computer which has the Process Monitor chart open, or that encounters an alert condition while entering data in the Work Set view. To send Process Monitor alerts for external data when the SPC software is not open, or to send Work Set alerts when the data entry computer is not email enabled, use the server-side SPC Service to monitor the database and send the alerts. Assuming you are using the SPC Service for sending emails, and have installed the SPC Service as instructed, start by verifying the setup:

Select Scheduled Tasks (from the Tools menu). In the Email tab, is the Enable Emails option checked? If so, verify the frequency at which the database will be checked for alert conditions and emails sent.
If the alerts are generated only through a Process Monitor analysis (such as for external (linked) data), verify the Enable Alerting in the Process Monitor Chart is enabled in the Scheduled Tasks' Alerting tab.
Review the Email Log (from Tools menu) to verify there are alerts that have been identified and not sent in the list. If there are emails in the queue that are not sent, continue to next step; otherwise review the first 2 steps.
Verify the SMTP settings have been properly defined (in the Preferences dialog from the Tools menu). Send a test email using the Add Email button from the Email Log.
Verify the SPC Service is running on the server (within the Control Panel's Administrative Tools / Services) . Try stopping the service and restarting it. After starting the service, verify that it is running properly using the Event Log (Control Panel / Administrative Tools / Event Viewer / SPC Server). If the service started correctly the following items are shown: "SPC Server: STARTING SERVICE" and "SPC Server: Connection to Database Successful" The Event Viewer will provide details as to whether emails were sent (which can also be verified in the Email Logs from the Tools menu).

Return to top

How do I hook up electronic gages or multiple gages via a multiplexer for rapid data entry?

Note: Some newer gages connected with so-called "smart cables", as well as multiplexors for connecting multiple gages, will serve as keyboard emulators. They are designed to write data to any software exactly as entering data through a keyboard. In these case, you do not need to setup a gage connection as described below. Instead, the data can be directly input into the current cell of a spreadsheet or data entry form in the Explorer or Work Set views. Check your manufacturer's specifications to see if this applies to your equipment.

You'll use the Add Gage option from the Gage branch to setup an initial gage.

Enter a valid name on the General tab, and leave the Active Status=True;
On the Interface tab, select the Serial Interface check box, then the Generic/Universal option from the Device list box. Set the COM or USB port used by the multiplexer (from Windows Device Manager) and its communication settings (from manufacturer’s docs);

If you are unsure of the COM port, start with COM 1. Use the OK button to save the selection.
Open the Test Gage tab. Use the Connect button to connect to the port, then use the gage Send button to send a reading to the port. If the correct COM port has been selected, you would see the text string including the measurement in the text box provided.
If no measurement string is visible, repeat steps 2-1 and 2-2 (above) for a different COM port (e.g. COM 2, then COM 3, etc.).

You’ll use the Generic tab to strip out extra characters, and to define where in the string this particular gage’s readings will occur. Use the Connect button on the Test Gage tab to look at the unaltered string from the multiplexer to determine the settings needed on the Generic tab.
For a multiplexer with multiple gages, or whenever you have similar gages to setup, use the Duplicate Gage option from the Gage branch to copy the settings from the first gage to a second gage. For a second gage connected through a multiplexer, adjust the slot location information for the second gage on its Generic tab.

The tricky part is Step 3, the Generic tab settings, but once you get it down it will be easy for the remaining gages. If you click the Help button from the Generic tab it will provide some specifics on the slot location settings and other fields in the dialog box.

Return to top

In the calibration software, how do I document an external calibration source?

To document an external calibration source, define a new Traceability Field (e.g. External Calibration) in the Traceability branch, then apply this to the gage via the Settings button.

Return to top

Is the size of the database a concern for performance?

Performance does not degrade noticeably with the size of the database, at least within reasonable limits. Instead, performance is dictated by the amount of data being analyzed in the current workset charts. We have generated a large database to demonstrate performance: 288 processes, 384 characteristics, and 48,466 data records. When the charts had the usual 100 or even 200 subgroups there was no noticeable degradation in performance as compared to the much smaller sample database.

Although it is fair to say that MS-Access is not ideally suited for large number of users, or large number of records, you can easily circumvent that by using several databases throughout the plant for the different departments, or through periodic use of the archive function to move older data records to a separate database.

It is also recommended to frequently repair and compact databases using the QACompact.exe application included in the installation (usually in the Program Files folder and available via shortcut). Download the QACompact.exe application.

Versions 3.1 and later support the use of SQL Server databases, which are particularly useful for larger databases or frequent transactions.

Return to top

Importing an MDB file into SQL Server

NOTE: This section is for upgrading an existing SPC Explorer/QA-Calibrate Access (MDB) database to a SQL Server database. Perform this section if you originally used SPC Explorer/QA-Calibrate with an Access database and wish to convert it to SQL Server.Note that you must purchase the SQL Server-enabled license of the software to store your data on SQL Server. To create a new (blank) SQL Server database, use the New Database option from the Database Properties window within the SPC Explorer/QA-Calibrate software.

Import the MDB into SQL Server using the Import Wizard in Enterprise Manager.

In SQL 2005: Run Enterprise Manager; Select the SQL Server where you want to import the data; Right-Click on the Databases Folder and select All Tasks... / Import Data... from the menu.
In SQL 2008: Select the Import and Export Data option within the Microsoft SQL Server 2008 group in the Start menu.
When prompted for Data Source select Microsoft Access and browse to the MDB file you want to import.
When prompted for a Destination select the Microsoft OLE DB Provider for SQL Server (SQL 2005) or SQL Server Native Client 10.0 (SQL2008); these are usually selected by default.
Type in the name of the SQL Server (usually provided by default).
Select the authentication method you wish to use (must have database creation permissions).
For Database select . This will prompt you for a database name. All other values can initially be left as default.
Select Copy Table(s) from the source database.
Select All the Tables and Views.
Select Run Immediately and the import will begin.

Set the Primary Key and Identifier field for each of the tables (the SQL Server Import utility does not do this automatically).

Using Enterprise Manager (SQL2005) / SQL Server Management Studio (SQL2008), select the database that was just imported.
Select the Tables icon to get a listing of all the tables in the database.
In Tools->Options->Designers->Table and Database Designers, uncheck the option for "Prevent saving changes that require table re-creation".
Right-Click on the first table and select Design Table from the menu.
Within the design window right-click on the top field (the table's ID field) and select the Primary Key menu option.
Also within the design window select the Identity checkbox for this top field to indicate it is a unique identity field within the table.
Close the design window and when asked to save select Yes.
Repeat these steps for every table in the database. (The system tables beginning with "sys" can be ignored).

The default SQL Server installation is not configured for remote access to the database, which is needed whenever you access the data from third-party applications like our SPC software.

First, enable named pipes on the SQL Server by typing “Run SQL Server Configuration Manager” into the Search field on the Task Bar. Use the Enter button to run the program SQLServerManager12.msc. In the SQL Server Configuration Manager that opens, expand SQL Native Client 11.0 Configuration (or whichever Native Client version is applicable to your SQL Server version), then, in the Client Protocols, check that TCP/IP is Enabled and Named Pipes is Enabled. (See also https://msdn.microsoft.com/en-us/library/ms181035.aspx.
Next, enable remote connections on the SQL Server by running SQL Server Management Studio; select the server name, then the Properties option from the right mouse menu. In the Connections page, ensure the Allow remote connections to this server option is selected, with a suitable timeout period entered (e.g. 600 seconds). Use the OK button to save the changes. See also http://www.top-password.com/blog/how-to-enable-remote-connections-in-sql-server/

For general information on troubleshooting SQL Server connections, see also http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx

Setup each client to open the new database on SQL Server:

To use Microsoft SQL Server for the SPC-PC IV Explorer database each client must have SQL Server Native Client installed. (The Native Client is backwards-compatible, so the latest version (released for 2012 and not changed for 2014 or 2016) will work with earlier versions of the database server; however, install the 32-bit (Download SQL Server Native Client for 32-bit computers ) or 64-bit (Download SQL Server Native Client for 64-bit computers) instance based on the client computer's operating system).
Update the license to allow use of SQL Server.

Select the spcsf.exe application file in Windows File Explorer, then select the Run As Administrator option from the right mouse menu.
Select the Update License option from the Help menu. Verify the Elevated field indicates True (if False, then you didn't open in RAA mode), then enter the new license code provided (also listed on the My Software page after login to the company account on our website).

Select the Database label at the top of the Explorer view left pane, then the Properties option to open the Database Properties window in the Explorer view's right pane.

Use the Open Database button on the Database Properties window’s Database tab
The updated license code previously-applied will now allow you to select the MS SQL Server (Native Client) option.
Select the OK button, and you are prompted to enter the Database Server Name (e.g. SQLExpress).
Select the Use SQL Server Authentication option, then enter the username (e.g. sa) and password, then select the Connect button to login to the SQL Server and see the list of available databases on the SQL Server
Select the new SPC database created on the SQL Server (e.g. SPCDB) from the Database list, then select the OK button to open the database.
You’ll then be prompted to enter your SPC Explorer username and password, which should be unchanged from the Access database.

Clean up the table constraints that are not properly transferred by the export. (This is done once to impact all users in the database).

Select the Application tab in the Database Properties window, then double-click on the Application Version label to open the Troubleshoot dialog box.
Select the SQL Constraint button to update the tables.
Exit the Troubleshoot dialog box.

Set a common SQL Server user account for SPC User login. (This is done once to impact all users in the database).

When logged into the SPC software as a user with Administrator privileges and with the SQL Server database opened, open the Preferences dialog (Tools menu).
On the Database tab, enter the username and password for the sa account (or any other account that allows for read and write privileges to all fields in the database) into the Login Using fields. Users will then use that account to access the SQL Server database, and will not be prompted separately to log into the SQL Server.

Return to top

Is SPC Explorer compatible w/ QS 9000?

QS 9000 Element 4.20 (Statistical Techniques) requires the use of statistical methods where applicable for analysis of quality-related operational data, as well as for on-going evaluation of Quality Management System effectiveness. Our SPC-PC IV Explorer software can be used to analyze both types of data,.

The formulas used in Quality America's SPC applications are in agreement with those found in the AIAG SPC Reference Manual (referenced by the QS9000 documentation). The Foreword to the AIAG SPC Reference Manual states the manual "should be considered an introduction to statistical process control. It is not intended to limit the evolution of statistical methods suited to particular processes or commodities, nor is it intended to be comprehensive of all SPC techniques."

In this regard, Quality America's SPC software does offer analysis options not discussed in the Reference Manual. These include non-normal Individual-X charts, non-normal Process Capability analysis, additional Run Test rules, etc. These options may or may not be used, at the user's discretion. Furthermore, the Reference Manual refers to some analysis techniques not offered in Quality America's SPC software, such as Median Charts, or to optional features such as Measurement System Analysis (offered in the QA-Calibrate software add-on to SPC-PC IV Explorer).

Return to top

Has SPC-PC IV Explorer been validated?

The US Food and Drug Administration (FDA) requires software validation for particular applications of software. Users seeking to meet these requirements should review our recommendations for FDA compliance.

Return to top