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.

 

 

 

SAS Innovate 2025: Call for Content

Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!

Submit your idea!

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.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

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