Data Link Properties: Connection

Use the Connection tab in the Data Link Properties dialog box to define the name, location, and type of the data to which you want to connect. When you select UNICOM Intelligence DM-n OLE DB Provider (where n is the version number) on the Provider tab, an UNICOM Intelligence-specific Connection tab is displayed.

Defines the type of metadata. The list shows the types of metadata for which you have a metadata source component (MDSC). The default options are:

Choose this option if you want to connect to case data only.

Selects metadata that is in an ActiveX Data Objects (ADO) data source.

Selects metadata that is in an IBM SPSS Statistics.sav file.

Selects metadata in a standard UNICOM Intelligence log file.

Selects metadata that is in the standard UNICOM Intelligence Data Model format, which is a questionnaire definition (.mdd) file.

Selects metadata that is in a UNICOM Intelligence Interviewer project's Sample and HistoryTable tables.

Selects metadata that is in a mrScriptMetadata file.

Selects metadata in a Quancept.qdi file using the QDI/DRS DSC.

Writes the metadata in an MDM document to a Quancept script (.qqc) file.

Writes the metadata in an MDM document to a Quantum specification.

Selects metadata that is in a Quanvert database.

Writes the routing section of an MDM document to a script that defines the routing required for interviewing.

The name and location of the metadata. The way you specify this depends on the type of metadata that you selected in the previous list. Click Browse to select the file in the Open dialog box.

The name and location of a .adoinfo file, which is an XML file that specifies the connection string for the target data source and the name of the target table in that data source. For more information, see the ADO DSC section of the UNICOM Intelligence Developer Documentation Library.

The name and location of the log file. Typically log files have a .tmp filename extension. However, some log files may have another filename extension. If necessary, you can rename the file so that it has a .tmp filename extension.

The name and location of the .mdd file.

The name and location of a Participants Report Document (.prd) file, which is an XML file that specifies the connection string and the names of the table and columns to be used.

The name and location of the script file.

The name and location of the .qdi file.

The name and location of the qvinfo or .pkd file.

The name and location of the .sav file.

By default, the metadata is opened in read-only mode. Select this option if you want to be able to write to it. When you open some types of data (for example, a Quanvert database) the metadata is always opened in read-only mode.

Opens the Metadata MDM Properties dialog box, where you can specify the versions, language, context, and label type to use. For more information, see Data Link Properties: Metadata Properties.

Defines the type of case data. The list shows all of the types of case data for which you have a case data source component (CDSC).

If you have specified a Metadata Type and a Metadata Location, and the default data source in your metadata refers to the case data that you want to connect to, you don't need to specify a Case Data Type or a Case Data Location.

The default options are:

Reads case data from an ActiveX Data Objects (ADO) data source.

Writes case data in tab-delimited format to a .csv file.

Reads and writes case data in a UNICOM Intelligence relational database in SQL Server. This option can be used to read data collected using UNICOM Intelligence Interviewer.

Selects the Log DSC, which enables you to read UNICOM Intelligence log files.

Reads and writes case data in an XML file. Typically, you use this option when you want to transfer case data to another location.

Reads case data in a Quancept.drs, .drz, or .dru file using the QDI/DRS DSC.

Selects the Quantum DSC, which reads and writes case data in a Quantum-format ASCII file.

Selects the Quanvert DSC, which reads data in a Quanvert database.

Reads and writes case data in an IBM SPSS Statistics.sav file.

The name and location of the case data. The way you specify this depends on the type of case data that you selected in the previous list:

The OLE DB connection string for the ADO data source. To build this string, click Browse, which opens a second Data Link Properties dialog box in which you can choose the options for your data source. For example, to connect to a Microsoft Access database or a Microsoft Excel file, select Microsoft OLE DB Provider for ODBC Drivers in the Provider tab and click the Build button in the Connection tab to build a connection string that uses the Machine Data Source called “MS Access Database” or “Excel Files” as appropriate. If your data source is a SQL Server database that is not a UNICOM Intelligence relational database, select Microsoft OLE DB Provider for SQL Server in the Provider tab and enter the server name and database name in the Connection tab. Then click OK to close the second Data Link Properties dialog box and return to the Connection tab of the first Data Link Properties dialog box.

The name and location of the .csv file.

This must be an OLE DB connection string. For more information, see Connecting to a relational MR database using RDB DSC 2.

The name and location of the .xml file.

The name and location of the .drs, .drz, or .dru file.

The name and location of the .dat file. If a .dau file is created, it will have the same name, but with the file name extension of .dau.

The name and location of the qvinfo or .pkd file.

The name and location of the .sav file.

This text box should be blank, unless you are connecting to one of the following case data types:

If you are connecting to a SQL Server database (that is not a UNICOM Intelligence relational database) or a Microsoft Access database, enter the name of the database table that you want to use. If you are connecting to a Microsoft Excel file, enter the name of the worksheet that you want to use, for example, Sheet1. Depending on the version of Excel installed, you may have to add a dollar sign ($) after the worksheet name for the connection to be successful, for example, Sheet1$.