Data Link Properties: All

You can use the All tab in the Data Link Properties dialog box to edit all of the available connection properties. However, generally you define the values for the properties on the Connection and Advanced tabs.

The length of time, in seconds, to wait for the initialization to complete.

The CDSC name to be used with the connection. This is the internal name of the CDSC (for example, mrRdbDsc2).

The full or relative path to an MDM document (.mdd) file or a metadata source for which an MDSC is available (in which case the name of the MDSC should be given in the MR Init MDSC property).

The name or location of the data source. For file or directory-based data stores, this is the path to the file or directory. The Data Model will treat a relative path as being relative to the metadata file specified in the Initial Catalog property. If Initial Catalog is not set, the Data Model will treat a relative path as being relative to the current directory. The Data Model resolves a relative path to an absolute path before passing it to the CDSC. For OLE DB-based data stores, this is the OLE DB connection string.

When a relative path is provided, you must apply a formula in order to calculate the absolute path:

To calculate the metadata's absolute path, take the MRS file path (the current path) and add the Initial Catalog's relative path in adoConn.open. For example, when the MRS script resides in the C:\scripts folder, the MDD file is stored in C:\scripts\Data.

To calculate the case data's absolute path, you must know what is specified for the DBLocation in the metadata (MDD). You must then apply the following formula:

If DBLocation of the metadata = Location of the adoConn.open Then
Absolute path of case data = Absolute path of mdd + Location in adoConn.open
Else
Absolute path of case data = Absolute current path of the mrs script + Location in adoConn.open
End If

When the formula is applied to the example script (assuming the script resides in C:\scripts), the script resembles the following:

Dim TableDoc, adoConn
set TableDoc=CreateObject("TOM.Document")
with Tabledoc
with .DataSet
'The following 3 lines are used to set the DBLocation of the Temp.mdd only
.Load(".\Data\museum.mdd",,".\Data\museum.ddf","mrDataFileDSC")
.MdmDocument.DataSources["mrDataFileDSC"].DBlocation=""
.MdmDocument.Save(".\Data\Temp.mdd")
end with
set adoConn=CreateObject("ADODB.Connection")
adoConn.Open("Provider=mrOleDB.Provider.2;Data
Source=mrDataFileDSC;Location=.\Data\museum.ddf;Initial Catalog=.\Data\Temp.mdd;MR Init MDSC=")
end with

With .MdmDocument.DataSources["mrDataFileDSC"].DBlocation=""

Absolute metadata path: C:\scripts\Data\Temp.mdd

Absolute case data path: C:\scripts\Data\Data\museum.ddf. The path results in an error because the museum.ddf file actually resides inC:\scripts\Data. Because the DBLocation path is the same as the Location path, the path defaults to the metadata path (C:\scripts\Data) plus the Location parameter path of theadoConn.open (\Data + \Data).

Without .MdmDocument.DataSources["mrDataFileDSC"].DBlocation=""

Absolute metadata path: C:\scripts\Data\Temp.mdd

Absolute case data path: C:\scripts\Data\museum.ddf . The path is valid because the DBLocation and Location paths are different. The formula calculates the case data absolute path based on the MRS script path plus the relative path of the Location parameter of the adoConn.open.

This is used internally to filter the CDSCs in the Data Link Properties dialog box, so that only read-enabled CDSCs are listed when the Mode setting is read, for example. Other uses of this property are reserved for future use.

The password used to connect to the data source.

The User ID used to connect to the data source.

The dirty data write mode. Allowing dirty data generates warnings rather than errors when dirty data is encountered. This setting is ignored if the value of the MR Init Validation setting is False. The default value is False.

Specifies whether the Data Model is to output category values or names. The default value of 0 indicates that the values are used. A value of 1 indicates that the names are used. This property can be used only if MDM mapped values are selected for the MR Init Category Values property.

Specifies whether the MDM mapped category value are used or whether the native values are used. The default value of 0 indicates that the MDM mapped category values should be used. A value of 1 indicates that the native values should be used. If no MDM Document is available, the native values are used. What the native values represent depends upon the DSC and the nature of the underlying case data. The native values may represent the actual raw values stored in the case data. However, this is not always possible and then the native values are identifiers for the categories.

This property is used by several UNICOM Intelligence DSCs to access special settings provided by the client application. For example, this property is used by RDB DSC 2 to specify whether the connection mode should favor memory usage or speed. (The default favors speed.)

This property can also be used by third party DSC developers to pass custom initialization information to their DSCs.

The locale ID to use when parsing input data.

Specifies the access mode for the MDM document being loaded from a .mdd file. A value of 0 specifies that the MDM document should be opened for read-only access. A value of 1 specifies that the MDM document should be opened for read/write access, and any changes will be written back to the .mdd file when the connection is closed. A value of 2 specifies that the MDM document should be opened for read/write access, but any changes will not be written back to the .mdd file. The default access mode is 0, read-only access.

The current context to be used for the connection.

The Data Model automatically searches the MDM Document for a DataSource object whose CDSCName property matches the value specified in the Data Source connection property and whose DBLocation property matches the Location connection property. This property defines what action the Data Model is to take if a matching DataSource object is not found. See About the MDM DataSource object for more information.

The current label type to be used for the connection.

The current language to be used for the connection.

The version of the MDM document to load. The value of this property can also be an expression that defines two or more versions to be combined as a superversion to load. For more information, see Version expressions.

This property is used to specify whether the MDM version variable should be enabled. The MDM version variable is an autogenerated derived variable that is enabled using the IDocument.EnableMetadataVersion Variable property. The default value of False indicates that the version variable is not enabled and a value of True indicates that the version variable is enabled. The version variable is named DataCollection.MetadataVersion. For more information, see “System variables”.

The MDSC to be used to load the metadata defined in the Initial Catalog setting. This property is ignored if Initial Catalog is not specified. For more information, see DSCs supplied with the UNICOM Intelligence Data Model.

Specifies the access mode for the MDM document being generated by the MDSC. A value of 0 specifies that the MDM document should be opened for read-only access. A value of 1 specifies that the MDM document should be opened for read/write access, and any changes will be written back to the MDSC when the connection is closed. A value of 2 specifies that the MDM document should be opened for read/write access, but any changes will not be written back to the MDSC. The default access mode is 2.

When an MDSC is being used to generate the MDM document, the Data Model ignores the MR Init MDM Access setting.

Specifies whether the native objects in the underlying database should be exposed directly as Data Model variables, without any interpretation. The default value of False indicates that the DSC should represent native database objects in a way that makes most sense in the Data Model. A value of True indicates that the DSC should expose native database objects without interpretation. For example, if a value of True is specified, a multiple dichotomy set in a .sav file would be represented as several long or text variables instead of one categorical variable.

The locale ID to use when formatting output data, such as error or warning messages.

Specifies whether the CDSC deletes the output data if it exists, before writing new data. The default value of 0 indicates that the CDSC should not overwrite existing data, but only append to the output data, if it exists. A value of 1 indicates that the CDSC should delete the output data and schema, which allows output data to be created with a different schema. A value of 2 indicates that the CDSC should delete any existing data records, but retain the native schema if possible. For some CDSCs, such as the Delimited Text DSC, the schema will be lost when the data is deleted, so the result will be the same for values of 1 and 2.