About NDS

LinusH · ‎04-26-2013

Since it seems it's not SAS that is the issue, you might find answers in a different forum. The average SAS user have no experience with SQLite...;-)

Tom · ‎08-22-2012

Are you sure you are not looking at the LABEL on the variable instead of its NAME? Try this code with and without the label statement. And notice the difference in the label assigned to the new AGESUM variable. proc summary data=sashelp.class; var age; label age='AGE'; output out=want sum(age)=agesum; run; proc contents data=want; run;

FloydNevseta · ‎05-10-2012

One problem could be related to how the data is transferred between unix and windows. In a windows text file, each line of data is terminated with a carriage return (CR) and line feed (LF). But in unix the line terminator is just a LF. I've had instances when someone ftp'ed files to me from windows to unix, and the files still contained the dos terminators (CRLF). That caused problems reading the data. On the infile statement, I added the option termstr=crlf so that SAS would recognize the dos terminators. Maybe that will work for you. I have a feeling that the embedded CR is affecting your output.

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: SQLite using Pipes

SQLite using Pipes

Re: PROC SUMMARY not creating new variable names in OUTPUT statement

Re: PROC SUMMARY not creating new variable names in OUTPUT statement

Re: PROC SUMMARY not creating new variable names in OUTPUT statement

PROC SUMMARY not creating new variable names in OUTPUT statement

Re: PROC EXPORT putting some variables on separate rows in csv file

Re: PROC EXPORT putting some variables on separate rows in csv file

Re: PROC EXPORT putting some variables on separate rows in csv file

PROC EXPORT putting some variables on separate rows in csv file

Re: SQLite using Pipes

Re: PROC SUMMARY not creating new variable names in OUTPUT statement

Re: PROC EXPORT putting some variables on separate rows in csv file