similar to: Part II Re: read.ssd {foreign} (Reading a permanent SAS d ataset into an R data frame)

Scot, Thanks for the additional information. On further reflection... whether one uses SAS PROC EXPORT or uses a SAS LIBNAME yourfile XPORT 'yourpathname'; statement, an intermediate file is created in either case. As far as experience tells me now, PROC EXPORT is a far superior choice, because variable names do not get truncated and you only have to deal with reading in a simple text

Hi, I am trying to read a SAS version 9.1.3 SAS dataset into R (to preserve the SAS labels), but am unable to do so (I have read in a CSV version). I first created a transport file using the SAS code: libname ces2 'D:\CES Analysis\Data'; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc

I have encountered a problem reading SAS transport files on both a Mac (OS X) and Linux (RedHat 9), both using R2.0.1. After loading "foreign", the command: read.xport("V1622101_050304.xpt") yields: Error in lookup.xport(file) : File not in SAS transfer format In Linux, I can "cat" the file. The first few lines are: **COMPRESSED** **COMPRESSED** **COMPRESSED**

Scot, Thanks for the info. I will try your code out to verify the result, but before I do that, will your code (SAS and R) work with variable names that are longer than 8 characters long without truncating the variable name in R? Also, I wonder about using your method or the PROC EXPORT method with larger data sets. The data sets I will be working with for the most part will not be that large,

I am attempting to read in a SAS 9.1 data file. After starting R I change to the directory containing the sas data file and use the "dir" command to confirm that it is there. Then I run the following R-code: library(foreign) sashome <- "/Program Files/SAS/SAS 9.1" test<-read.ssd(file.path(sashome), "pcb", sascmd = file.path(sashome,

Even though the FDA has no policies at all that limit our choices of statistical software, there is one defacto standard in place: reliance of the SAS transport file format for data submission (even though this format is deficient for this purpose, e.g., it does not even document value labels or units of measurement in a self-contained way). Because of the widespread use of SAS transport files in

try: library(foreign) read.ssd("J:\\QM\\Reports\\Sarthur\\SAS_Application\\SAS_Data_Sets","use") instead, hth, Merry Christmas, Bernhard -----Original Message----- From: Stephen Arthur [mailto:sarthur67 at yahoo.com] Sent: 20 December 2002 16:55 To: ripley at stats.ox.ac.uk; rossini at blindglobe.net Cc: r-help at stat.math.ethz.ch; stvjc at channing.harvard.edu Subject:

-------- 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

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")

Hi, I am encountering a confusing problem when I tried to use read.ssd to read SAS datasets. For one SAS dataset "a.sas7bdat", it did not work; while for another SAS dataset "b.sas7bdat" it worked: > tmp<-read.ssd("C:\\SASdata", "a",sascmd="C:/Program >Files/SAS/SASFoundation/9.2/sas.exe") SAS failed. SAS program at

> On Apr 14, 2018, at 12:18 PM, WRAY NICHOLAS via R-help <r-help at r-project.org> wrote: > > > -------- 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

> On Apr 13, 2018, at 10:01 AM, WRAY NICHOLAS via R-help <r-help at r-project.org> wrote: > > 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

Hello I am sure this is elementary, but I can't figure it out..... I am using SAS v8.2 and R 1.4.1 on a Windows platform. I have a large (6 megabyte) file in .sd2 format. I want to import it into R. If necessary, I can create a smaller file, as I don't need all the variables that are in this file I downloaded the package foreign. I then tried to use PROC CPORT in SAS to create a

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

Colleagues During the transition to R3.0.0 (OS X), one of the packages that I used -- SASxport -- did not work until I used the "type=source" option in install.packages. This led to an adventure: 1. I downloaded the package source: SASxport_1.2.4.tar.gz 2. in the SASxport/R folder, I found all the functions that are part of the package. I became interested in whether I could

Full_Name: Ruskin Chow Version: R 2.0.1 OS: Windows 2000 Submission from: (NULL) (203.169.154.66) Data imported from SAS using read.xport() in package foreign are converted to <NA> when the SAS data field consists of character strings that are only one character long. This is apparently a previously reported bug and perhaps fixed in some platform other than Windows (rw2001).Some

The Details. In the following version. > version _ platform i386-pc-linux-gnu arch i386 os linux-gnu system i386, linux-gnu status major 1 minor 8.1 year 2003 month 11 day 21 language R > lookup.xport ignores some datasets in sas export file. File "emptySasData3.xpt" (available at http://biostat.mc.vanderbilt.edu/tmp/emptySasData3.xpt) is a

{Note the DATE ! this message bounced ... because it was sent to R-announce which was definitely the wrong list anyway. MM - your list maintainer } Dear R-Team I have installed R version 0.990 and the foreign package under Windows NT.. Whilst lookup.xport() works as it should, read.xport() crashes reporting an "access error" as well for larger datasets as also for small

Hi, SAS transport files created with the xport engine in SAS can be read using read.xport. However, the xport engine only works with SAS version 6, and consequently long variable names are not allowed... Can anyone tell me how to get SAS data (ver 8) into R (easily)? Thanks in advance S?ren H?jsgaard sorenh at agrsci.dk http://www.jbs.agrsci.dk/~sorenh

I am trying to import data from a SAS XPORT file that contains 24 SAS files. When I use the "read.xport" procedure only about 16 data frames (components) are created. Any suggestions? ************************************************************************* Gary A. Nelson, Ph.D Massachusetts Division of Marine Fisheries 30 Emerson Avenue Gloucester, MA 01930 Phone: (978)