search for: sasxport

Dear Rxperts,.. I am using R 3.0 in both 32- and 64-bit Windows 7 environment and have trouble using SASxport. They seem to work fine under R.2.15.3. ....The error/warning messages are provided below... Following are the messages obtained when trying to read s SAS transport file (.xpt) library(SASxport) Warning message: package ‘SASxport’ was built under R version 3.0.1 read.xport(fname) Error in...

Hello all, I have got some data in SAS, and I export it to one excel workbook with multiple sheets, for example, each sheet has the sales information for each state. Then I need to use R to do plotting, analysis on those sales data, where I need to load the data from excel to R. When I read the article at this link:

...S data distribution. He seemed to think I was confused about the function you had been using. The reason I mentioned that `read.xport` was from the 'foreign' package is that one generally loads that package to make the function available, while it appears you were using a different package, SASxport, and I didn't know whether that package had a function which had the same name as the one from pkg-foreign, and if it did whether it might depend on the read.xport function in foreign. You should not need to download the 'foreign' package, since it ships with every distribution of R. Th...

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") Alfalfa<-read.xport("test.xpt") I have set the directory correctly as far as I am aware, b...

.../bin/view/Main/ChangelogHmisc and http://biostat.mc.vanderbilt.edu/twiki/bin/view/Main/ChangelogDesign . These versions pass R CMD check for the latest R-devel so I expect they will work on the next production release of R. Of special note is the Hmisc sasxport.get function's new method='csv' argument. This works with a SAS macro to use SAS PROC EXPORT to export an entire data library, and handles variable and value labels, date, time, data/time variables [for dates, the new R Date class is now used as is also now used for sas.get, sp...

.../bin/view/Main/ChangelogHmisc and http://biostat.mc.vanderbilt.edu/twiki/bin/view/Main/ChangelogDesign . These versions pass R CMD check for the latest R-devel so I expect they will work on the next production release of R. Of special note is the Hmisc sasxport.get function's new method='csv' argument. This works with a SAS macro to use SAS PROC EXPORT to export an entire data library, and handles variable and value labels, date, time, data/time variables [for dates, the new R Date class is now used as is also now used for sas.get, sp...

i am trying to convert sas file into csv. I used write.csv(a, file="cool.csv") but nothing come out. i don't know why. Thanks. library(Hmisc) a<- sasxport.get("C:\\Users\.....") write.csv(a, file="cool.csv") -- View this message in context: http://r.789695.n4.nabble.com/convert-the-sas-file-into-csv-in-R-tp3311769p3311769.html Sent from the R help mailing list archive at Nabble.com.

Hello, I wanted to ask help about importing sas datasets. 1)I tried with some functions as read.ssd (foreign package), but it doesn't import the file if the length of the variables' names are longer than 8 bite (it has to conform to the 6 version). 2)I then tried with the sas.get function (Hmisc package) but with the command: c<- sas.get(lib="c:\\ghan",

...two formats. The files were sent in both SAS xport and STATA, thanks, I am told, to stat-transfer. The two files, ostensibly, contain the same data, just in different formats. My goal: Move these files to MySQl without the help of SAS or STATA (which I do not have). The tools I am using are: 1. sasxport.get from Hmisc 2. read.dta from foreign 3. dbWriteTable with the MySQL driver to create and populate the tables. The import and table creation went well, though the SAS file created all text field types in the MySQl database. (I am not sure if this is a characteristic of the original data set or...

> 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 me to read the xpt file into R: > > library(SASxport) > data(Alfalfa) > lookup.xport("test.xpt") > Alfalfa<-read.xport("test.xpt") > > I have set th...

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

Hi! I'm trying to start a credibility estimation study with a coule of data sets that are created for SAS. The data sets are saved as ".sas7bndx" and ".sas7bdat". I've tried reading them to R with the function 'read.xport' but this returns the error message 'Error in lookup.xport(file) : unable to open file'. Are there any other functions that one

...filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc cport data=ces2.fadata file=transp; run; I then tried to read it in R using: > library(foreign) > library(Hmisc) > fadata2 <- sasxport.get("D:\\CES Analysis\\Data\\fadata.xpt") Error in lookup.xport(file) : file not in SAS transfer format Next I tried using the libname statement and the xport engine to create a transport file. The problem with this method is that variable names cannot be more than 8 characters as th...

I'm writing an R extension. The language I'm using is ANSI C. One of the functions I'm writing will accept a string and return a dataset as a dataframe. i.e the prototype will be of the form: dataframe foo(R_String) { } Does anyone have any skeleton code for such a function, i.e. one that receives an R "string" and returns a dataset as a dataframe ? The main concerns I

Hi All, Sorry that I didn't provide enough information. I've been trying to import SAS xport files that contain multiple files using package foreign's read.xport. I first attempted this back in 2005 and had problems. Some of files that were present in the SAS xport file weren't being created in R. I submitted my problem to the community:

I am using R-2.10.1 binary from CRAN on a WinXP Pro system. I also use SAS v9.2 on the same box. I just started using the SAS ODBC driver that comes with version 9 of SAS. I have been able to set up an ODBC source for SAS datasets using the driver, and then with RODBC I am able to read a sample SAS dataset. > library(RODBC) > ch <- odbcConnect('sasodbc', believeNRows=FALSE)