search for: sasv5xpt

...quot;RA" "RE" "SA" "SL" The following datasets were not read by lookup.xport UR, URN, VIS, VIT, VO. The example of the SAS code used to builds the empty data from the non-empty data in "export.xpt". options nofmterr; proc options;run; libname x sasv5xpt "H:\projects\export.xpt"; libname y sasv5xpt "H:\projects\emptySasData3.xpt"; data ae; set x.ae(obs = 0); run; ... data vit; set x.vital(obs = 0); run; data vo; set x.volume(obs = 0); run; proc copy in = work out = y; run; I think I did not miss anything, thank you, Svetlana...

...minor 6.1 year 2002 month 11 day 01 language R and using foreign 0.5-8 I am encountering errors when using read.xport. Here's code for producing SAS transport files for testing: libname x SASV5XPT "test.xpt"; libname y SASV5XPT "test2.xpt"; PROC FORMAT; VALUE race 1=green 2=blue 3=purple; RUN; PROC FORMAT CNTLOUT=format;RUN; data test; LENGTH race 3 age 4; age=30; label age="Age at Beginning of Study"; race=2; d1='3mar2002'd ; dt1='3mar2002 9:31:02...

...roblem with lookup.xport when there are multiple files. The documentation states that a list with a major element for each dataset will be created. read.xport is supposed to create a list of data frames for this case. Here is SAS code I used to create test files, followed by R output. libname x SASV5XPT "test.xpt"; libname y SASV5XPT "test2.xpt"; PROC FORMAT; VALUE race 1=green 2=blue 3=purple; RUN; PROC FORMAT CNTLOUT=format;RUN; data test; LENGTH race 3 age 4; age=30; label age="Age at Beginning of Study"; race=2; d1='3mar2002'd ; dt1='3mar2002 9:31:02&...

...one of the data frames but the data were read incorrectly. The XPORT files come from ftp://cusk.nmfs.noaa.gov/mrfss/intercept/ag/ if anyone wants to try it. I used the .xpt in "int82ag.zip" (all years except 1985,1988 and 1989 are read incorrectly) and it appears they were created using SASV5XPT. Once imported, look in data frame I3_19822 which should have only 3650 records, but there are 76,187 records. I am using version: platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32...

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)

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