BookmarkSubscribeRSS Feed
zhanghaipo
Fluorite | Level 6
Thank you very much for your help. I try not to use stata files to avoid this.
zhanghaipo
Fluorite | Level 6
Thank you very much for your help. If I get a solution, I will share it.
ChrisNZ
Tourmaline | Level 20

Any reason you're not using UTF-8? This seems to be the standard where data is converging. This would make your data universal.

xxformat_com
Barite | Level 11

I don't have the explanation.

I can just share with you that I also have that kind of message when using dbms=xlsx with proc import.

I don't have the message

  • when using the xlsx engine in the libname statement or
  • when using dbms=excel with proc import.

The value for of my global encoding option is UTF-8.

Current version: 9.04.01M5P091317

 

Tom
Super User Tom
Super User

SAS datasets have two types of variables.  Floating point numbers and fixed length character strings. When you convert a XLSX file the columns that SAS guesses should be convert to character variables will be. 

 

So you can just ignore that message.  The programmer at SAS that wrote that was confused.

 

 

 

hackathon24-white-horiz.png

2025 SAS Hackathon: There is still time!

Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!

Register Now

How to Concatenate Values

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.

SAS Training: Just a Click Away

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

Browse our catalog!

Discussion stats
  • 19 replies
  • 11252 views
  • 3 likes
  • 6 in conversation