Desktop User Guides > Professional > Data management scripting > Working with UNICOM Intelligence Interviewer - Server data > Exporting UNICOM Intelligence Interviewer - Server data to IBM SPSS Statistics
 
Exporting UNICOM Intelligence Interviewer - Server data to IBM SPSS Statistics
Exporting UNICOM Intelligence Interviewer - Server data to an IBM SPSS Statistics .sav file is not fundamentally different from other exports to a .sav file. However, there are some things you need to aware of when working with data collected using multiple versions.
Multiple exports to the same .sav file
There are some restrictions on running multiple exports to the same .sav file:
The structure of the input metadata in the second and subsequent exports must exactly match the structure of the input metadata used for the first export. Even a small change in the input metadata, like the addition of a single category, might make the next export fail. In practical terms this generally means that you must export the data collected with each major version to a different .sav file or you must use the same set of versions for the export. The UNICOM Intelligence Developer Documentation Library comes with sample .mrs files for listing and comparing the versions in an .mdd file. For more information, see Listing and comparing versions.
When exporting batches of data to the same .sav file, you need to use the output metadata from the first export as the input metadata for the second and subsequent exports.
If you specify a subset of the variables to transfer, you must specify exactly the same set of variables for all of the transfers to the same .sav file.
If you export the same records to the same .sav file two or more times, the new records are appended to the end of the file and the existing records are not updated. You should therefore be careful not to create duplicate records in the .sav file by exporting the same case data to it more than once.
Using the same alias names as a previous export
When there is a version change and you start exporting to a new .sav file, you might want as far as possible to use the same alias names in the new .sav file variables as used in the previous one. Doing this requires a special type of merge of the newest version in the project's .mdd file with the metadata used for the previous version's exports. For an example of doing this, see the mrInterviewNextBatchNewVersionToSav.dms sample. For more information, see Sample DMS files for exporting UNICOM Intelligence Interviewer data.
Exporting all data at the end of a project
In a multiversion project, you can export data for all versions after all of the data has been collected using all of the versions. For more information, see Exporting UNICOM Intelligence Interviewer - Server Data to IBM SPSS Statistics Using All Versions.
Exporting batches of data
In a large or ongoing project, you might want to export data in batches, for example on a daily basis. The UNICOM Intelligence Developer Documentation Library comes with some samples that you can use to do this. For more information, see Exporting batches of UNICOM Intelligence Interviewer - Server data to IBM SPSS Statistics.
See
Exporting UNICOM Intelligence Interviewer - Server Data to IBM SPSS Statistics Using All Versions
Exporting batches of UNICOM Intelligence Interviewer - Server data to IBM SPSS Statistics
Working with UNICOM Intelligence Interviewer - Server data