When the HTMLDocType property is set to UseTemplateDocType, the HTML DocType that is specified in the layout template is used. When the property is not specified, the HTML Player reverts to its previous behavior of using the web.config file setting (if present), or to the default DocType. For more information, see HTMLDocType and HTMLOptions custom properties.

Improved support for long and categorical variable native WHERE clauses. For more information, see WHERE expressions supported natively.

A new MR Init Native Filter connection property was added to the UNICOM Intelligence OLE DB Provider. For more information, see Connection properties.

RDB DSC 2 schema. The schema has been updated to support the Publish Data feature via the Categories table and CategoriesLookup table.

The Relational MR Database CDSC now supports unexpanded loops for reading and writing data. The UNICOM Intelligence Data Model 7.0.1 hierarchical data features are only available for the RDB DSC 2 schema and the hierarchical view of the data is available only when an MDM document is attached. For more information, see Upgrading older databases to the RDB DSC 2 schema.

Because the RDB DSC2 does not support unexpanded level variables under expanded level variables, another version of the household.mdd file and associated, backup relational database have been added to the UNICOM Intelligence Developer Documentation Library. These new files are installed to: [INSTALL_FOLDER]\IBM\SPSS\DataCollection\7\DDL\Data\RDB

The loop variable person in these new files have been updated from mlExpand to mlLevel in MDM2 Explorer.

The Relational MR Database CDSC now supports some types of WHERE expression natively, which can improve performance when filtering data for tabulation. For more information, see WHERE expressions supported natively.

In the past, the Relational MR Database CDSC could represent hierarchical data only in a flattened form in the VDATA virtual table. Now RDB DSC 2 can represent hierarchical data in HDATA hierarchical virtual tables. However, unbounded loops (which are loops for which the maximum number of iterations is unknown) are currently unsupported and the hierarchical view of the data is available only when an MDM document is attached. For more information, see Understanding hierarchical data and Loops, grids, and levels.

UNICOM Intelligence Data Model 2.7 comes with an OLE DB implementation of this CDSC in addition to the older ODBC-based implementation. The new OLE DB implementation is called RDB DSC 2 (the internal name is mrRdbDsc2). The existing ODBC implementation of this CDSC is essentially unchanged from UNICOM Intelligence Data Model 2.6.

RDB DSC 2 reads and writes case data through OLE DB and has the following main advantages over the older ODBC implementation:

RDB DSC 2 can read and write data in existing RDB databases using the UNICOM Intelligence Data Model 2.6 schema. However, when writing data to a new database, RDB DSC 2 automatically uses a new, improved schema. For more information, see Relational MR Database CDSC schema. Note that the new schema is inaccessible to the older ODBC-based RDB DSC, which means it is inaccessible to UNICOM Intelligence Data Model 2.6 and earlier. You can optionally ugrade existing databases to the new schema. For more information, see Upgrading older databases to the RDB DSC 2 schema.

When writing data, RDB DSC 2 creates a second SQL Server connection, because this offers a significant performance improvement compared with using a single connection.

Connecting to RDB DSC 2. When you connect to RDB DSC 2, you need to specify the Location connection property as an OLE DB connection string. You can also set the MR Init Custom connection property to favor either memory or speed. If you do not set this property, the favor speed mode will be used. For more information, see Connecting to a relational MR database using RDB DSC 2.

Case-insensitive databases. When using RDB DSC2, the LIKE keyword always searches text case-sensitively, regardless of the collation option chosen when SQL Server was installed.

Transferring data from older databases without an .mdd file. Changes in the Metadata Model (MDM) in UNICOM Intelligence Data Model 2.7 mean that it is not possible to transfer data from a relational MR database that was created in UNICOM Intelligence Data Model 2.6 or earlier without using an .mdd file. For more information, see Known problems in Relational MR Database CDSC.

Schema change. The schema has increased the number of tables from five to six. The new table is called OtherID and holds the maximum value in the database of OtherID, the unique identifier used in the OtherData table. This improves performance when writing records. For more information, see OtherID table.

New stored procedures. There are a number of new stored procedures. For more information, see Stored procedures.

Increased size limit for text responses. In UNICOM Intelligence Data Model 2.3 and earlier the limit for text responses was 2000 bytes (999 characters). This limit has now been raised to 8000 bytes (4000 characters).

Schema changes. The schema has increased the number of tables from three to five. The new tables are:

Case-sensitive databases. Relational MR Database CDSC supports SQL Server that has been installed with the case-sensitive collation option. However, note that if you are using this option, you must enter column names with the correct case in queries and the LIKE keyword will search case-sensitively. However, the UNICOM Intelligence Find.

Case-insensitive databases. Generally the LIKE keyword searches text case-sensitively. However, when SQL Server has been installed with the case-insensitive collation option, the LIKE keyword generally searches case-insensitively. For example, the following query is evaluated case-insensitively:

However, when the LIKE keyword is included in a complex expression (for example, one that includes a function from the UNICOM Intelligence Function Library) it is evaluated case-sensitively:

This behavior has not changed in UNICOM Intelligence Data Model 2.4, but was previously undocumented. This anomaly does not exist in RDB DSC 2.

For further information on expression evaluation, supported SQL queries, and the UNICOM Intelligence Function Library, see the UNICOM Intelligence Developer Documentation Library.

Connecting using an ODBC connection string. When connecting to a database using Relational MR Database CDSC in UNICOM Intelligence Data Model 2.4 and later, you can specify the Location connection property using an ODBC connection string instead of a data source name (DSN). This makes it easier to export data from a relational MR database using SQL Server Data Transformation Services (DTS), because you generally no longer need to set up a DSN for the database first because the ODBC connection string is automatically written to the .mdd file when the database is synchronized. For more information, see Connecting to a relational MR database.

Supported features. The documentation has been updated to list details of which CDSC features are supported. For more information, see Relational MR Database CDSC: Supported CDSC features.

Setting custom properties in the connection string. All global properties can now be set in the connection to the SPSS Statistics SAV DSC. For more information, see Properties and settings used by the SPSS Statistics SAV DSC.

Unlabeled values in SAV data. When reading categorical variables, the default behavior of the SPSS Statistics SAV DSC has changed. To avoid the potential for data loss when the case data contains values that do not match a predefined category, the SPSS Statistics SAV DSC now does the following:

Determining Categorical Variables. Three new properties have been introduced to control how the determines which variables are categorical. These properties apply only when generating an MDM document from the .sav file or accessing the case data with no metadata. For more information, see Determining categorical variables.

Invalid Language Settings. When asked to use a language that is not supported on the current computer, the default behavior of the SPSS Statistics SAV DSC has changed. Instead of continuing and producing garbled text, the now issues an error message and stops. You can amend the behavior to match that of previous versions of the SPSS Statistics SAV DSC. For more information, see Invalid language settings.

SavLanguage and SavCodePage Properties. These existing properties can now also be set in an MDM document or in the connection string. For more information, see Properties and settings used by the SPSS Statistics SAV DSC.

ImportFactors Property. When generating MDM Elements from a SAV numeric variable's labeled values, this new property can be used to specify that the element's Factor property will be set to the labeled value if it is non-missing. For more information, see Properties and settings used by the SPSS Statistics SAV DSC.

You can now use the DataFormat custom property in your card, column, and punch definitions. By setting the DataFormat to "numeric," you can export categorical variables as numerics. For more information, see Card, column, and punch definitions.

Hierarchical view of the data. The new Table Services DSC is used to provide a hierarchical (HDATA) view of the data for the Quantum DSC and other CDSCs that support only a flat (VDATA) view. As a result, data accessed using the Quantum DSC will be treated as hierarchical in UNICOM Intelligence Reporter. For more information, see Table Services DSC.

Update capability. Quantum DSC can now update numeric variables in an existing Quantum-format ASCII file. You can use this capability to add weights to a Quantum file. The UNICOM Intelligence Developer Documentation Library is supplied with a sample Data Management Script file called QuantumWeighting.dms that demonstrates how to do this. For more information, see Sample DMS files.

Read capability. Quantum DSC can now read response (case) data from any Quantum-format ASCII file. You can use the read capability to analyze your Quantum data in UNICOM Intelligence Reporter or to transfer your Quantum data to any other data format supported by the UNICOM Intelligence Data Model. You must first create a questionnaire definition (.mdd) file that contains card, column, and punch information that accurately describes the format and contents of your Quantum file. For more information, see Reading from a Quantum file.

MDSC capability. Quantum DSC has been extended to include MDSC capability. This means that it is now able to write out a Quantum specification based on the card, column, and punch definitions in the .mdd file. You can use this functionality to write out a Quantum specification in a script, such as a DMS file. For more information, see The Quantum specification.

Performance improvements. UNICOM Intelligence Data Model 2.8 includes internal changes to the CDSC to improve performance when transferring data.

Working with hierarchical data. In UNICOM Intelligence Data Model 2.8, Quantum DSC is not designed for use in data sets that cannot be represented in a flattened form. For example, it is not designed for use with Quanvert levels projects or other metadata that contains unbounded loops (Array objects of type mlLevel).

Improved date handling. Quantum DSC previously exported date variables as the numeric values in which the data is stored internally. Unfortunately these numeric values are not easily readable. Quantum DSC now formats all date and time values as a numeric value with the following format YYYYMMDDhhmmss, where YYYY is the year, MM is the month, DD is the day, hh is the hour, and so on. This is an internationally recognized date format and has the advantage that it is readable and easy to sort.

Improved serial number handling. Quantum DSC now uses the SerialFullName custom property to get the name of the variable to be used as the serial number. This is particularly useful when you are using Quantum DSC to export non-UNICOM Intelligence data to Quantum, because it means you can use any suitable variable as the serial number regardless of its name. (You can specify the variable to be used in Metadata Model to Quantum.) Previously, the serial number variable had to be called Respondent.Serial.

Improved handling of card, column, and punch definitions. Improvements mean that it is now easier to manage the definitions in projects in which questions and categories are added and deleted between versions. For more information, see Card, column, and punch definitions.

Reading old Quanvert projects. The Quanvert DSC now reads projects that were created in a version of Quanvert before version 1.6.

Setting the MDM base language. The Quanvert metadata source component (MDSC) now supports several different methods for specifying the base language in the generated MDM document. For more information, see Language handling by Quanvert DSC.

CreateMddFromQuanvert.mrs. This mrScriptBasic script, which is included with the UNICOM Intelligence Developer Documentation Library can be used to create an MDM document (.mdd) file for an existing Quanvert project. The MDM document can then be used to load the Quanvert project into UNICOM Intelligence Reporter. For large Quanvert multiprojects, this approach will deliver much better performance compared with using the Quanvert MDSC to read the metadata. For more information, see Quanvert multiprojects.

Packed Quanvert project. The Household sample Quanvert project that comes with the DDL now includes a packed project file called househol.pkd. For more information, see Packed Quanvert projects.

Custom connection properties. The QDI/DRS DSC now supports a number of unique custom connection properties. For more information, see Custom connection properties used by QDI/DRS DSC.

Hierarchical view of the data. The new Table Services DSC is used to provide a hierarchical (HDATA) view of the data for the QDI/DRS DSC and other CDSCs that support only a flat (VDATA) view. As a result, data accessed using the QDI/DRS DSC will be treated as hierarchical in UNICOM Intelligence Reporter. For more information, see Table Services DSC.

Improved handling of invalid characters. QDI/DRS DSC now ignores certain characters if they appear in response texts. The characters that are ignored are exclamation mark (!), asterisk (*), equals sign (=), tab, and square brackets ([ and ]).

Dates and times. QDI/DRS DSC now reads dates and times correctly.

Better names for loop iterators. The names assigned to loop iterators now match those generated by other DSCs, for example, loop[{Brand_1}].loop.

Category names. QDI/DRS DSC now creates category names directly from the response texts, in the same way as other DSCs. Earlier versions created category names of the form rnumber. This change makes it much easier to specify filters on categorical data exported by QDI/DRS DSC.

.dru files. QDI/DRS DSC no longer reports errors when reading .dru files.

Card and column information. QDI/DRS MDSC now adds card and column information as custom properties.

Better handling of records containing dirty data. When reading .qdi or .drs files that contain dirty data, using select * from vdata now returns all records but leaves blanks for data that is incorrect. Previously, no records were returned.

Dealing with missing files. QDI/DRS DSC now issues an error message and exits if it is not given a valid MDM document or if the file location connection property is empty.

Improved category names. QDI/DRS DSC now bases the category names on the unique ID, if there is one, and otherwise on the response text. This means it is easier to link the categories to the responses in the original data than in previous versions (where categories were given arbitrary names of the form r1, r2, r3, and so on.).

Problems resolved. A number of problems have been resolved. These include some problems related to reading Other Specify and open-ended data.

DBASE questions. This question type is typically used in Quancept CATI interviews for very large product lists, such as models of cars or printers. The list of categories is stored in a database and the .drs file stores the response that was chosen as a numeric value that identifies the category in the database list. In UNICOM Intelligence Data Model 2.4, these responses were stored in a text variable. However, in UNICOM Intelligence Data Model 2.5 and later, they are stored in a numeric variable, which makes it easier to analyze the results.

Improved nested loop handling. In UNICOM Intelligence Data Model 2.4, QDI/DRS DSC could not read .qdi files that contained nested loops (loops within loops). In UNICOM Intelligence Data Model 2.5 and later, QDI/DRS DSC can handle .qdi files that contain loops with one level of nesting.

Names of Quancept loop variables. In UNICOM Intelligence Data Model 2.4, the names of variables that are part of a Quancept loop construction were prefixed with the text "Array_". In UNICOM Intelligence Data Model 2.5 and later the names of the variables are no longer prefixed in this way.

Improved handling of Other Specify responses. In UNICOM Intelligence Data Model 2.4, QDI/DRS DSC stored only the text responses to an Other Specify category and any coded responses were ignored. In UNICOM Intelligence Data Model 2.5 and later, QDI/DRS DSC handles the coded responses to an Other Specify category correctly.

Double quotation marks in category names. In UNICOM Intelligence Data Model 2.4, QDI/DRS DSC ignored any responses that start or end with a double quotation mark ("). For example, QDI/DRS DSC would ignore a response with the text "With difficulty". This problem was resolved in Data Model 2.5.

Improved handling of unasked questions. In UNICOM Intelligence Data Model 2.4, QDI/DRS DSC incorrectly returned an empty categorical value ({}) for responses to categorical questions that respondents had never been asked (for example, because they had been routed around them). In UNICOM Intelligence Data Model 2.5 and later, QDI/DRS DSC returns a NULL value for unasked categorical questions.

Improved error handling. In UNICOM Intelligence Data Model 2.4, when an unexpected problem was detected in a case data record, QDI/DRS DSC sometimes rejected all of the subsequent records in the file. Improved error handling means that this should no longer happen. The error messages have also been improved.

There are no significant updates.

You can now query concurrent activity usage from log files with DM Query. For more information, see Querying concurrent activity usage from logs with DM Query.

When viewing all the log (.tmp) files in a folder, you can now restrict the files viewed by applying a date and time filter or a file type filter (for example, view only ISE and IVW log files). The custom connection properties associated with these features are FileDateFilter and FileTypeFilter. For more information, see Custom connection properties used by Log DSC.

When viewing all the log (.tmp) files in a folder, you can now include log files in sub folders by specifying the SearchSubFolders custom connection property. This property is useful for viewing the log files for a cluster that has a separate sub folder for each server's log files. For more information, see Custom connection properties used by Log DSC.

The Component IDs topic has been updated to reflect new IDs introduced in UNICOM Intelligence 2.0. For more information, see Component IDs.

You can now optionally specify a folder as the data location when you connect to the Log DSC. When you do this, Log DSC includes all of the files that have a .tmp filename extension in that folder. This is useful in the following situations:

Example SQL queries now includes an example query that sorts the log entries by date and time. This is useful when you are viewing all of the log files in a folder.

Three new variables, Project, RespondentId, and InterviewId, have been added to the metadata. Log DSC now parses UNICOM Intelligence Interviewer log files, splitting the custom fields into separate variables. The new variables will contain a NULL value for log entries that do not contain the UNICOM Intelligence Interviewer custom fields. For more information, see Log variables.

In addition, Log DSC now supports files with a .log filename extension.

Quancept MDSC supports the eval function that may be used to embed expressions in Quancept scripts, which will not be evaluated until the interview is running. The embedded expressions can be any expression that is supported by the UNICOM Intelligence Evaluate component. For more information, see Expression evaluation.

UNICOM Intelligence Data Model 2.7 comes with an improved version of Quancept MDSC, in which a number of problems have been resolved.

The objects in the DSC Registration component (mrdscreg2.dll) enumerate the available DSCs by checking the Registry for installed DSCs.

The IMDSCCapability interface has one new method (Transform) and one new property (Transform). See IMDSCCapability in the MDM Object Model Reference. These are provided to support a standard way of invoking components that modify MDM documents.

In order to support MDSCs that can write metadata in native formats and convert metadata to other in-memory formats such as a string containing a script, the IMDSCCapability interface now has four new methods (Load, Save, ConvertToMetadata, and ConvertToData) and one new property (CanConvert). For more information, see IMDSCCapability.

Metadata Model to Quantum name change. MDM2Quantum has been renamed to Metadata Model to Quantum.

Categoricals. You can now allocate categoricals using different data formats (including fill zero on the left). Valid data formats for single categoricals are Numeric, Literal, and Punch. Valid data formats for multiple categoricals are Numeric, BitString, and Punch. A new global option on the Preferences dialog allows you to allocate all categoricals as numerics. Updates to the Edit Variable dialog allow you to set CodeWidths and Values. This also impacts the Data Map and Quantum specifications. For more information, see Allocating card, column, and punch Codes manually.

Enhanced grid support. The data map now uses FullLabel instead of Label for better grid support.

Precision and scale. Precision and scale is now used in determining the column count.

Column range. The column range has been increased to support additional formats beyond Quantum.

Triple-S export support. Support has been added for allocating columns for multipliers to support Triple-S export. For more information, see Support for Triple-S export.

Shared lists. You can now allocate shared lists separately for each question.

You can now export categorical variables as numerics through the DataFormat custom property. When DataFormat is set to "numeric," the variable is exported with the value set in the Value custom property. If the Value property is not set, the value is determined by combining the column offset and punch.

Differences in data types when importing a data map. If a variable has the same name in both the currently open document and the data map file being imported, but the data types are different, Metadata Model to Quantum issues an error message. Errors of this type do not immediately halt the import process; instead, Metadata Model to Quantum continues attempting to import the data map and displays the errors at the end of the procedure. For example, if the currently open document shows the age variable as being numeric but the import data map shows it as categoric, the error message will be "age expected to be type Lng. Is of type Cat."

Support for UNICOM Intelligence Interviewer 3 (IOM) question features. Metadata Model to Quantum supports the additional question and response features available with UNICOM Intelligence Interviewer 3, including the option

Enhanced facilities for reading and writing files. The Metadata Model to Quantum component now supports the following methods:

Events. The new methods for reading from files can raise the following events:

Error codes. Three new error codes have been added to ErrorConstants. These codes are returned by the new methods described earlier.

The Metadata Model to Quantum component has been ported to Visual Basic .NET in order to provide better interaction with browser-based applications. This change should be invisible to users but has the advantage that developers who use .NET can now use the assembly instead of the COM interop.

Multiple response variables. Changes in UNICOM Intelligence Data Model 2.7 led to a problem when the ExplodeMultiPunch option was used in a document that had one or more shared lists that were used in both single and multiple response questions. To resolve this problem, the AllocateCardColPunch and AllocateVariables methods now allocate the punch codes on the ElementInstance objects of multiple response variables rather than the Element objects.

Multiplier variables. The AllocateCardColPunch and AllocateVariables methods now allocate multiplier variables (these are sometimes found in data sets that originated in Quanvert). In previous versions of the UNICOM Intelligence Data Model, multiplier variables were ignored.

Creating the Quantum specification. The new MDSC feature of the Quantum DSC means that it is now easy to create a basic Quantum specification programmatically. The Metadata Model to Quantum sample mrScriptBasic files have been updated to provide examples of doing this. For more information, see Creating an Quantum specification using a script.

Working with hierarchical data. In UNICOM Intelligence Data Model 2.8, the Metadata Model to Quantum component is not designed for use in data sets that cannot be represented in a flattened form. For example, the Metadata Model to Quantum component is not designed for use with Quanvert levels projects or other metadata that contains unbounded loops (Array objects of type mlLevel).

Improved Quantum specifications. Metadata Model to Quantum now uses the new MDSC feature of the Quantum DSC to create the Quantum specification. As a result, a number of problems have now been resolved and you may notice a few minor differences compared to previous versions. For example:

In addition, you can now select the user context and language to be used for the texts in the specification. For more information, see General preferences.

Using Metadata Model to Quantum with UNICOM Intelligence Interviewer - Server Admin. Changes in UNICOM Intelligence Interviewer - Server Admin 2.1 mean that the recommendations for how to use Metadata Model to Quantum with UNICOM Intelligence Interviewer - Server Admin have changed. For more information, see Using Metadata Model to Quantum with UNICOM Intelligence Interviewer - Server Admin.

Working with hierarchical data. In UNICOM Intelligence Data Model 2.8, Metadata Model to Quantum is not designed for use in data sets that cannot be represented in a flattened form. For example, Metadata Model to Quantum is not designed for use with Quanvert levels projects or other metadata that contains unbounded loops.

Punch definitions. Metadata Model to Quantum now writes punch definitions to the DataSourceProperties collection on the Element rather than the ElementInstance object. This change is largely invisible because the MDM inheritance rules mean that DataSourceProperties on the ElementInstance object inherits from the Element object. However, this change has affected the handling of variable instances that share a category list with other variable instances (for example, when a variable instance is part of a grid or loop or uses a shared category list). If you clear or allocate an individual variable instance that shares a category list with any other variable instances, the punch and column offset details for those other variable instances will be silently updated too.

However, this change has the advantage that the categories in category lists that are shared between questions have the same punch codes in each question and has led to a significant reduction in .mdd file size in projects that have large numbers or grids, loops, or defined lists.

Punch errors. Metadata Model to Quantum continues to write the punch error codes to the DataSourceProperties collection on the ElementInstance objects. This means that CheckCardColPunch can mark individual element instances in a grid whose punch definitions are inconsistent. However, CheckCardColPunch does not do a similar consistency check on the element instances that are in a loop or part of a shared list.

System variables. In Data Model 2.6 and earlier, the elements in the categorical system variables had built-in punch and column offset definitions. These have been removed in UNICOM Intelligence Data Model 2.7 because they resulted in different punch allocations being made depending on whether or not they were cleared before allocation. However, the card and column definitions that are built into the system variables themselves are unchanged, except that the column count built-in to the DataCollection.Status system variable has been increased to 10 to make it compatible with the ExplodeMultipunch option.

Improved version handling. When you open a file that has more than one version, Metadata Model to Quantum now lists the available versions and lets you choose the version or versions you want to work on. By default, the version or versions you selected last time are automatically selected for you. For more information, see Version handling in Metadata Model to Quantum.

Improved handling of shared category lists. Category lists are frequently shared between questions and variables. For example, all of the subquestions in a categorical grid question share the same category list and when the same category list is required by several questions, it is often set up as a shared list (sometimes called a defined list). In UNICOM Intelligence Data Model 2.6 and earlier, the punch and column offset details were allocated and stored separately for each category in each variable. In UNICOM Intelligence Data Model 2.7, they are now allocated and stored only once for each category in a category list that is shared. This has the advantage that the categories will always have the same punch codes and has led to a significant reduction in .mdd file size in projects that have large numbers or grids, loops, or defined lists.

Improved handling of system variables. The system variables have the column count definition built-in. In UNICOM Intelligence Data Model 2.6 and earlier, they also had punch and column offset definitions built-in. However, this lead to an anomaly whereby Allocate Cols and Punches defined different punch codes depending on whether you had run a clear in the session or not. Therefore in UNICOM Intelligence Data Model 2.7, the system variables no longer have punch and column offset definitions built-in. In addition, the column count built-in to the DataCollection.Status system variable has been increased to 10 to make it compatible with the Explode Multipunched Questions option.

Order of variables. Changes to the MDM in UNICOM Intelligence Data Model 2.7 mean that you may see differences in the order in which variables that relate to the same question or loop are displayed in the Metadata Model to Quantum window. For example, in the museum_qq.mdd sample there is a question called School that has an Other Specify category. In the metadata the School question has three helper variables: School.Other, which is a text variable for storing the open-ended responses to the Other Specify category, School.Other.Codes, which is a categorical variable for storing the coded responses to the Other Specify category, and School.Other.SourceFile, which is used to store the name of the file that contains an image of the scanned response. In UNICOM Intelligence Data Model 2.6, Metadata Model to Quantum listed the variables in this order:

Whereas in UNICOM Intelligence Data Model 2.7, they are listed as follows:

You may notice similar changes in the order in which the variables that belong to a grid or a loop are displayed. This change also affects the order in which the card and column allocations will be made. However, Metadata Model to Quantum will not overwrite any existing allocations if you choose the option to keep previous allocations. For more information, see Allocate Cols and Punches.

Opening other types of data. You can now open in Metadata Model to Quantum any type of data for which you have a read-enabled MDSC. For example, you can now open a .sav file in Metadata Model to Quantum. Metadata Model to Quantum uses the to create an MDM document from the .sav file and you can save the MDM document as an .mdd file. For more information, see Opening a file or database of another type.

Specifying the serial number variable. When you open a file that does not include the Respondent.Serial system variable, you can now specify which variable is to be used as the serial number variable. This is useful when you are using Metadata Model to Quantum with non-UNICOM Intelligence data. For more information, see Select Serial Variable.

Clearing individual variables. You can now clear the card, column, and punch allocations on one or more individual variables. For more information, see Clearing one or more individual variables.

Improved version handling. Metadata Model to Quantum no longer creates a new version when you open a questionnaire definition file in which the most recent version is locked. Now Metadata Model to Quantum gives you the option of creating a new version prior to clearing old-style card, column, and punch definitions from the most recent version of the questionnaire definition.

Improved handling of errors by Allocate Cols and Punches. When there is not enough space for a variable (for example, because it requires more columns than are available on the card) Allocate Cols and Punches now sets the column count to the number of columns that the variable requires. This makes it easier to resolve the problem.

Allocate separate card for Codes variables. This option no longer affects the allocation of the coding variables associated with Other Specify categories. For more information, see Card and Column preferences.

New Close command. There is now a Close command on the File menu. You can use this command to close a file without closing the Metadata Model to Quantum window.

The main changes since UNICOM Intelligence Data Model 2.4 are:

Internal changes. The part of the program that writes the card, column, and punch information to the questionnaire defininition is now contained within a separate COM component, called the Metadata Model to Quantum Component. This has been done to make it easier to allocate card, column, and punch definitions programmatically: for example, in a DataManagementScript (DMS) file.

Improved error checking. Metadata Model to Quantum now performs better error checking and there are now more possible error codes. For more information, see Metadata Model to Quantum error codes.

Punch code errors. The element grid in the Manual Allocation dialog box now has an Error Flag column. When an element has a punch code error, it is now displayed in this column. (You need to use the scroll bar to be able to see the Error Flag column.) For more information, see Allocating card, column, and punch Codes manually.

New shortcut menus. You now get a shortcut menu when you right-click in the Metadata Model to Quantum window or the grid in the Manual Allocation dialog box. These new shortcut menus provide handy commands for changing the allocations for several variables or elements at once. For more information, see Metadata Model to Quantum shortcut menu.

Card and Column Preferences. The CardColumns tab in the Preferences dialog box has some new options. For more information, see Card and Column preferences.

Quantum Specification Preferences. The Quantum tab in the Preferences dialog box has two new options. For more information, see Quantum Specification preferences.

Version Selection. The Select Version option in the Tools menu lets you choose which version of the questionnaire definition you want to work on if you do not want to allocate cards and punches based on the latest version. For more information, see Version Selection. This option replaces the View Version History option which has been removed.

In addition, the documentation of Metadata Model to Quantum has been improved:

Metadata Model to Quantum 2.3 comes with UNICOM Intelligence Data Model 2.4. The main changes since Metadata Model to Quantum 2.0 (which came with UNICOM Intelligence Data Model 2.2 and 2.3) are:

Version handling. Metadata Model to Quantum has been changed to improve its handling of questionnaire definitions that have multiple versions and is now integrated with the Metadata Model Version Utility. For more information, see Version handling in Metadata Model to Quantum.

Allocating punch codes. You can now allocate punch codes to individual categories manually. For more information, see Allocating card, column, and punch Codes manually.

Automatic allocation. The Overwrite Existing Columns and Codes option has been removed from the Preferences dialog box and you now specify whether you want to overwrite the existing allocations when you run the Allocate Cols and Punches command. This change has been made to give increased flexibility and to reduce the risk of overwriting allocations inadvertently. In addition the way the command allocates card, column, and punch codes has been improved. For more information, see Allocate Cols and Punches.

Quantum specification. You now define all of the options for the Quantum specification on the new Quantum tab in the Preferences dialog box. You can also choose which variables are to be included in the export and the export itself has been improved. For more information, see Export Quantum Specification.

Log file. Metadata Model to Quantum now writes an entry to a log file after each operation that changes the card, column, and punch definitions in the questionnaire definition. For more information, see Metadata Model to Quantum log file.

Data map. The data map feature has been improved and now includes punch code information. For more information, see Using the Data Map.

View menu. Metadata Model to Quantum now has a new View menu, which gives you convenient access to the the log file, the Quantum specs, the data map file, and the questionnaire definition version history. For more information, see Metadata Model to Quantum View menu.

Multilingual studies. In multilingual studies you can now choose the language in which to display the variable texts. If texts are available for use in more than one context, such as interviewing and analysis, you can also choose the context to use. For more information, see General preferences.

Integrity checking. The Check Cols and Punches command has been improved and it now checks the integrity of all punch code definitions for each categorical variable as well as the card and column definitions for all of the variables in the questionnaire definition.

Serial number. The serial number system variable (Respondent.Serial) is no longer shown in the Metadata Model to Quantum window because the serial number is automatically recorded in the serial field on every card. For more information, see Metadata Model to Quantum window.

In UNICOM Intelligence Data Model 2.8, the structural objects (such as the Document, Variable, and Array objects) have a new Script property. This is a read-write property that displays an mrScriptMetadata representation of the object and enables you to change the object by changing the mrScriptMetadata. Although this is just a "normal" property, MDM Explorer now shows the contents of this property in a new pane in the lower right corner of the MDM Explorer window. This makes it easy to view and change the mrScriptMetadata. For more information, see Working with mrScriptMetadata in MDM Explorer.

The text box that opens when you double-click a label now has multiple lines and can display the labels in HTML or plain text format.

MDM Explorer has a new Add Script method. This enables you to add a new object to a Fields, HelperFields, or Types collection using a script. For more information, see Working with mrScriptMetadata in MDM Explorer.

MDM Explorer now shows the following properties, which were introduced in UNICOM Intelligence Data Model 2.8:

The changes in the version of MDM Explorer that came with UNICOM Intelligence Developer Documentation Library - March 2003 are summarized below.

Opening a superversion. You can now open multiple versions of the metadata, as follows:

Opening files. It is now easier to reopen files because the new version of MDM Explorer has a recent files list.

Saving files. When you use the Save As command, the filename now defaults to the name of the file you are working on.

Setting a custom property's type. When you add or edit a custom property, you can now set its type by selecting an entry from a list box. More technical users can enter the OLE variant type directly into the text box. Note that setting a custom property's type to Empty removes the property.

Deleting a custom property. You can now delete a custom property by selecting it on the right side of the window and then pressing Delete. Alternatively, you can delete a custom property by setting its type to Empty.

New objects. MDM Explorer now shows the SelectedVersions and VersionSets objects, which were introduced in UNICOM Intelligence Data Model 2.7.

New properties. MDM Explorer now shows the following properties, which were introduced in UNICOM Intelligence Data Model 2.7:

Existing properties. In addition, MDM Explorer now shows the following properties, which were introduced in an earlier version of the UNICOM Intelligence Data Model:

Internal changes to the UNICOM Intelligence Data Model mean that the merging is now more consistent with the merging that occurs when you use the "superversion" feature introduced into the Metadata Model (MDM) in UNICOM Intelligence Data Model 2.7. As a result, you may notice some changes to the handling of conflicts that occur in the versions being merged. The most noticeable difference is that the order of the questions and categories is now always taken from the most recent version included in the operation and not from the version you define as the master. See The master version in a merge operation.