BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
programeerSAS
Fluorite | Level 6

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! 

 

ballardw
Super User

@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 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! 

 


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.

hackathon24-white-horiz.png

The 2025 SAS Hackathon has begun!

It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.

Latest Updates

Creating Custom Steps in SAS Studio

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.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 16 replies
  • 5977 views
  • 12 likes
  • 6 in conversation