Hi Kurt-
I use to code a lot in SAS but the import step had this one little problem on the raw data side that you identified spot-on!
I have never seen or used the
options validvarname=v7; but now I know it!
Thank you sincerely for repeatedly looking at my problem and solving it! You are a machine!
@programeerSAS wrote:
Hi Kurt-
I use to code a lot in SAS but the import step had this one little problem on the raw data side that you identified spot-on!
I have never seen or used theoptions validvarname=v7;but now I know it!
Thank you sincerely for repeatedly looking at my problem and solving it! You are a machine!
It is quite possible that you hadn't needed the option before. The validvarname option was established to handle, mostly, variables in external databases that allowed different variable naming conventions. Then some of the SAS interfaces lately have defaulted to the Validvarname=any which allows these other naming conventions. You may also run into issues with VALIDMEMNAME=Extend which allows other characters for data set and other file names though won't create member names with leading spaces.The option VALIDMEMNAME=compatible sets the "normal" SAS data set name rules.
April 27 – 30 | Gaylord Texan | Grapevine, Texas
Walk in ready to learn. Walk out ready to deliver. This is the data and AI conference you can't afford to miss.
Register now and lock in 2025 pricing—just $495!
Still thinking about your presentation idea? The submission deadline has been extended to Friday, Nov. 14, at 11:59 p.m. ET.
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.