Proc import column names

[ballardw]

Where is &first defined? Any you probably want it to be

category = "&first";  unless you have previously quoted it.

If you have gotten messages about undefined variables, since you're not showing any log results, it would be due to the value of first resolving to something like Television   (%let first=Television;) the Category=&first; resolves to

Category=Television; and if you don't have a variable named television then category is undefined.

[art297]

I just noticed it in the proc sql.  However, the proc sql code was designed to expect column names like a b c, etc.

Going with varnum, like Tom suggested, should get around the fact that some/all of the variables have names.

I'll stick with my last suggestion.

[LRN]

Hi Tom,

As Arthur said, I did make a small change in the proc import statement as follows and it worked great. Thanks to you and Arthur.

PROC IMPORT

        DATAFILE= &testfile

        OUT=&outdsn

        REPLACE

        DBMS=XLS;

    SHEET="Sheet1";

    GETNAMES=no;

  datarow=2;

RUN;

LRN