DATA Step, Macro, Functions and more

SAS dataset opens in SAS Enterprise but not in SAS 9.1

Reply
Occasional Contributor Doc
Occasional Contributor
Posts: 8

SAS dataset opens in SAS Enterprise but not in SAS 9.1

A colleague emailed me a SAS dataset which I copied to my desktop. I double click it and it opens just fine in SAS Enterprise. I can see all the variable names and the actual data.

But when I ask for the dataset to be opened in SAS 9.1 it says:

ERROR: Unable to open the table TMP1.exer. TMP1.exer cannot be opened. Do you want to select a different table to open.


I am confused. Because I do not understand enough. I would like to be able to read the dataset into SAS 9.1. Any ideas?
Trusted Advisor
Posts: 2,115

Re: SAS dataset opens in SAS Enterprise but not in SAS 9.1

Open the dataset again in EGuide. Select Properties and see how the dataset was created and give you an indication of your next step.

For instance, if you have multiple SAS datasets on your desktop and they were created with different engines, then you need different libnames for each engine type.

(Note that even if the files have the same extension, they may have been created with different engines.)
N/A
Posts: 0

Re: SAS dataset opens in SAS Enterprise but not in SAS 9.1

Hi Doc,

you have given the error pop-up when you tried to open the table.

can you please post the error showing in log window.

This problem occurs when BASE SAS not able to identify the formats assigned to the variables where SAS EG can do that.

I faced this problem before. we have reassigned the format for that particular variable and then we used that table in BASE SAS.

This is one possible reason for that ERROR

Hope this will help you

Regards,
skm
Valued Guide
Posts: 2,177

Re: SAS dataset opens in SAS Enterprise but not in SAS 9.1

Doc

is it possible the data set was read in E.G. from an excel file with special characters in a column name?
It seems by default E.G. applies system option [pre] validVarName= ANY [/pre] but a non-E.G. session uses V7 instead of ANY.
If you set your defaults (in so many ways) to ValidVarName=ANY, you may overcome the problem.

good luck

PeterC
Ask a Question
Discussion stats
  • 3 replies
  • 915 views
  • 0 likes
  • 4 in conversation