▪The samples reference various sample data files. If the sample data files are stored in a different location on your computer, you will need to edit the sample DMS files accordingly before running them.

▪You need UNICOM Intelligence Professional 7.5 installed to run these samples. Some of the samples have additional requirements. For example, the samples that read or write data in a relational MR database require access to a Microsoft SQL Server installation and appropriate user access rights; the samples whose names start with “MS” require one or more of the Microsoft Office applications to be installed; the table scripting samples require the UNICOM Intelligence Professional Tables Option. For further information, see the notes about each sample in the following topics.

▪The samples are set up to store the output files in the [INSTALL_FOLDER]\IBM\SPSS\DataCollection\7\DDL\ Output folder. This folder is generally created by the UNICOM Intelligence Developer Documentation Library installation. However, if this folder does not exist on your system, because, for example, you chose a custom installation, you must create the folder or edit the sample DMS files to specify a different folder that does exist.

▪Some of the samples are set up to create the log file in the C:\temp folder. If this folder does not exist on your system, you must create it or edit the sample DMS files to specify a different folder that does exist.

▪To help you identify the output files created by each sample DMS file, the output files generally have the name of the sample DMS file. For example, Weighting.dms creates output files called Weighting.mdd, Weighting.ddf, and Weighting.htm.

▪An error might occur if you try to run some of the samples more than once without first deleting or moving the output from the previous run. For example, transfers to a relational MR database might fail if you try to transfer a record with the same serial number (stored in Respondent.Serial) twice.

▪You can use the samples as a starting point when you develop your own DMS files. However, work on a copy of the files rather than working on the sample files directly. This means you will not lose your work when you uninstall or upgrade the UNICOM Intelligence Developer Documentation Library.

▪Some of the samples use Include files, sometimes with several text substitutions. You might find it easier to understand these samples if you look at the expanded file. You can save the expanded file without running it using the /a: and /norun options in DMS Runner.