27.03.2013 Views

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SPSS® 12.0 Command Syntax Reference

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Overview<br />

Options<br />

SAVE TRANSLATE 1461<br />

SAVE TRANSLATE translates the working data file into a file that can be used by other software<br />

applications. Supported formats are 1-2-3, Symphony, Multiplan, Excel, dBASE II,<br />

dBASE III, dBASE IV, tab-delimited ASCII files, SAS, and SPSS/PC+ data files.<br />

Variable Subsets. You can use the DROP and KEEP subcommands to specify variables to omit<br />

or retain in the resulting file.<br />

Variable Names. You can rename variables as they are copied to the spreadsheet, database, or<br />

tab-delimited ASCII file using the RENAME subcommand.<br />

Variable Map. To confirm the names and order of the variables saved in the resulting file, use<br />

the MAP subcommand. MAP displays the variables saved in the file next to their corresponding<br />

names in the working data file.<br />

Spreadsheet Files. You can use the FIELDNAMES subcommand to translate variable names to<br />

field names in a spreadsheet file.<br />

Value Labels. You can export value labels rather than values in spreadsheet files using the<br />

CELLS subcommand.<br />

SAS Value Labels. Use the VALFILE subcommand to create a SAS syntax file containing your<br />

data’s value labels. This option is available only when exporting to a SAS file type.<br />

Basic Specification<br />

• The basic specification is OUTFILE with a file specification in apostrophes.<br />

• TYPE and a keyword to indicate the type of dBASE file is also required to save dBASE<br />

database files.<br />

• The VERSION subcommand is optional, although it should be set for any format that has<br />

more than one version.<br />

Subcommand Order<br />

• OUTFILE or CONNECT must be specified first. OUTFILE is invalid for TYPE=ODBC and<br />

required for all other types. CONNECT is required for TYPE=ODBC and invalid for all<br />

other types.<br />

• The remaining subcommands can be specified in any order.<br />

Operations<br />

• The working data file remains available after SAVE TRANSLATE is executed.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!