Exporting the Quantum specification
1 From the Metadata Model to Quantum menus, choose File > Export Quantum Specs
2 In the Save Quantum Spec As dialog box, enter the name and location of the .run file. The name of the file must conform to the Borland 8.3 filename requirement. This means that it must not contain more than eight characters before the .run filename extension.
Metadata Model to Quantum creates several spec files. The names of the main files are based on the name of the .run file you enter here, but with different filename extensions (.tab, .qax, .ban, and .n10). However, include files are also created for any grid axes and these are based on the axis names. This means that if you export Quantum specifications for more than one questionnaire definition into the same folder, these grid axis include files will overwrite any that already exist with the same name. It is therefore generally preferable to use a different folder for each questionnaire definition file.
3 Click OK.
Metadata Model to Quantum automatically runs the Check Cols and Punches command before exporting the specification. If any errors are encountered, Metadata Model to Quantum displays a message and does not proceed with the export. You need to resolve the errors before attempting the export again. If no errors are encountered, the export proceeds and when it is complete, Metadata Model to Quantum gives you the option of viewing the spec files. For more information, see
View Quantum Specifications.
Notes
▪If you have added any variables to the Document since you last opened it in Metadata Model to Quantum, unfortunately those new variables will be excluded from the export by default. If you want to include the new variables in the Quantum specification, you need to select them in the Quantum Variable Selection or manual allocation dialog box or reapply your rules.
▪You need to allocate card, column, and punch codes for every variable in the questionnaire definition regardless of whether you are including them in the Quantum specification. This is because the card, column, and punch codes are used when exporting the case data. For the case data export to succeed, card, column, and punch codes are required for every variable.
See also