options MSGLEVEL=I;
proc import datafile= &originalfile
dbms=sav out=x replace;
run;
NOTE: VARCHAR data type is not supported by the V9 engine. Variable ID has been converted to CHAR data type.
NOTE: VARCHAR data type is not supported by the V9 engine. Variable STUDY has been converted to CHAR data type.
PROC IMPORT spits out that bogus "warning" about VARCHAR data types in other places. You can ignore it. So that message is probably NOT related to the problem you are having.
What version of SPSS made the file? Was it using UTF-8 characters (does that version of SPSS even support UTF-8 characters?)
What encoding is your SAS session using? Is it using UTF-8? Or some single byte encoding instead?
How did you move the SAV file from the machine that made it to the machine were SAS is tried to read it? Is it possible you copied the file as TEXT file instead of a BINARY file and corrupted the content? That used to be a common problem when moving files with FTP.
Don’t miss the livestream kicking off May 7. It’s free. It’s easy. And it’s the best seat in the house.
Join us virtually with our complimentary SAS Innovate Digital Pass. Watch live or on-demand in multiple languages, with translations available to help you get the most out of every session.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.