search for: saslib

...gt;<87>1<BC><87>S 0 0 20 CHAR In contrast, I can read.xport a different file successfully. That file (and others that I can import successfully) contains the following first line: HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 6.12 WIN_NT 21OCT02:13:30:0721OCT02:13:30:07 I know little about SAS but I wonder whether the problem relates to the export characteristics of different versions of SAS. If so, it appears that read.xport may not work with newer versions of SAS. If so, is there a...

...or "transfer format from SA is supposed to make reading data less difficult and standardized. This is what a header from the version used by the NHANES releases (that's all one line): > > HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.2 XP_PRO 16SEP09:09:39:2516SEP09:09:39:25 HEADER RECORD*******MEMBER HEADER RECORD!!!!!!!000000000000000001600000000140 HEADER RECORD*******DSCRPTR HEADER RECORD!!!!!!!000000000000000000000000000000 SAS...

Hi I'm trying to read SAS-data on VAX/VMS to Windows R using foreign pakage read.xport and experience some problems. Following lines are used in SAS to create XPORT file LIBNAME a ''xxx; LIBNAME b XPORT ''; PROC COPY IN=a OUT=b; RUN; and I succeed in getting file that looks like correct xport file.However when typing in R following

...the maximum number of variables for a dataset in R or for importing with read.xport, but I suspect this is the issue. For completeness, here is the start of the .xport file (it's all on one line): HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.1 SunOS If anyone has any insights into this, I would greatly appreciate it. Thanks! Mike Greene [[alternative HTML version deleted]]

...d on MAC, in this case the results are not rational. Many of the numbers are interpreted as INF etc. Is it possible that the SOLARIS to Linux is causing this problem? Here is a sample of the input file HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.1 SunOS 13JUN06:14:51:0313JUN06:14:51:03 HEADER RECORD*******MEMBER HEADER RECO RD!!!!!!!000000000000000001600000000140 HEADER RECORD*******DSCRPTR HEADER RECORD!!!!!!!000000000000000000000000000000 SAS...

...ort" or "transfer format from SA is supposed to make reading data less difficult and standardized. This is what a header from the version used by the NHANES releases (that's all one line): HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!000000000000000000000000000000 SAS SAS SASLIB 9.2 XP_PRO 16SEP09:09:39:2516SEP09:09:39:25 HEADER RECORD*******MEMBER HEADER RECORD!!!!!!!000000000000000001600000000140 HEADER RECORD*******DSCRPTR HEADER RECORD!!!!!!!000000000000000000000000000000 SAS...

Hello R folk I have an xpt file which I have been trying to open into R in R studio On the net I found guidance which says that I need packages Hmisc and SASxport which I have successfully loaded. I had also found some code which says that this would allow me to read the xpt file into R: library(SASxport) data(Alfalfa) lookup.xport("test.xpt")

-------- Original Message ---------- From: WRAY NICHOLAS <nicholas.wray at ntlworld.com> To: peter dalgaard <pdalgd at gmail.com> Date: 14 April 2018 at 20:18 Subject: Re: [R] Reading xpt files into R Well yesterday I'd downloaded the "foreign" package and tried to open the xpt file using that: library(foreign) read.xport("test.xpt") I got the following