topic Re: The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns. in SAS Studio

The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns.

ashish9541 — Thu, 26 Sep 2019 17:33:06 GMT

Unable to open data table

The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns.

Re: The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns.

ballardw — Thu, 26 Sep 2019 20:03:11 GMT

@ashish9541 wrote:

Unable to open data table

The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns.

How did the data set get created? Check the log when running code to see what happens. A data set created without any records or variables will say so in the log.

Example:

250  data work.junk;
251  run;

NOTE: The data set WORK.JUNK has 1 observations and 0 variables.
NOTE: DATA statement used (Total process time):
      real time           0.03 seconds
      cpu time            0.00 seconds

And how are you attempting to open the data set?

Re: The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns.

ashish9541 — Thu, 26 Sep 2019 20:21:34 GMT

I have tried using PROC as well as manually. This table comes with the learning data exercise, so not sure how data set created under data folder

Re: The table "_TEMP5.eu_occ" cannot be opened because it does not contain any columns.

ballardw — Thu, 26 Sep 2019 20:56:33 GMT

@ashish9541 wrote:
I have tried using PROC as well as manually. This table comes with the learning data exercise, so not sure how data set created under data folder

I suggest that you go back through any set up instructions, redo and check each step carefully as it appears the intended set may have been corrupted and you need to recreate the original data set.

Note: This sort of thing can be caused by your code while learning if you place the wrong data set name on any statement that creates output. Check the log frequently. As a new user that means for each proc or data step as it runs to see if you have output issues, such as the 0 observations.

If you write, or the training shows any code such as:

data somedatasetname;
    set somedatasetname;
/* other code goes here*/
run;

then that data step will completely overwrite an existing data set. So be very careful to not use the same name on the SET and DATA statements while learning.

Also a missing SET statement is a likely cause of 0 observations as shown in my previous post. It is very good practice to always explicitly list the data set used for source data, either with a SET statement in a data step or the DATA= option of almost every procedure.