similar to: SASxport v. 1.2.2

Displaying 20 results from an estimated 10000 matches similar to: "SASxport v. 1.2.2"

2007 Nov 01
0
SASxport v. 1.2.0
SASxport Version 1.2.0 is now available --------------------------------------- The SASxport package provides R with full support for reading and writing SAS xport format files. Version 1.2.0 corrects a critical issues with storage of negative numbers, as well as adding additional improvements to the handling of SAS display and input format specifications. With these enhancements, both reading
2007 Nov 01
0
SASxport v. 1.2.0
SASxport Version 1.2.0 is now available --------------------------------------- The SASxport package provides R with full support for reading and writing SAS xport format files. Version 1.2.0 corrects a critical issues with storage of negative numbers, as well as adding additional improvements to the handling of SAS display and input format specifications. With these enhancements, both reading
2013 Jun 20
0
Trouble with SASxport in R.3.0. under 32-bit and 64-bit Windows (both 7 and Vista)
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)
2013 Apr 11
4
Understanding contents of packages
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
2018 Apr 14
1
Fwd: Re: Reading xpt files into R
> 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
2018 Apr 13
5
Reading xpt files into R
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")
2008 Oct 09
1
Error when reading a SAS transport file
Dear All, I get the following error when using either SASxport or Hmisc to read an .xpt file: > w <- read.xport("D:/consult/Trophos/dnp/base/TRO_ds_20081006.xpt") Erreur dans factor(x, f$value, f$label) : invalid labels; length 15 should be 1 or 14 > z<- sasxport.get("D:/consult/Trophos/dnp/base/TRO_ds_20081006.xpt") Erreur dans factor(x, f$value, f$label) :
2018 Apr 13
0
Reading xpt files into R
> 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
2001 Dec 03
0
Segfault in foreign:read.xport (PR#1192)
I get a segfault when trying to read a SAS transport file with rather long rows using read.xport from package foreign (version 0.4-7). The culprit seems to be these lines in xport_read in SASxport.c: 590 } else { 591 c = strchr(tmpchar, ' '); 592 *c = '\0'; 593
2010 Dec 06
3
How to this SAS transport file in R?
Dear All, I try to read the SAS transport file in R, but it shows error. Please help! I am using R 2.11.1 library(foreign) download.file("http://isites.harvard.edu/fs/docs/icb.topic35387.files/demo_c.xpt","C:/Desktop/demo_c.xpt") sasxport <- read.xport("C:/Desktop/demo_c.xpt") Error in lookup.xport(file) : file not in SAS transfer format -- View this
2010 Dec 28
4
Reading sas7bdat files into R
Hi All, I am trying to import a .sas7bdat file into R. I tried using Hmisc package's sasxport.get() function. temp <- sasxport.get("path\abcd.sas7bdat") I get an error that says "Error in lookup.xport(file) : file not in SAS transfer format" I am not familiar with SAS transfer format. Could somebody please clarify what is it that I am missing, Thanks for your
2009 Feb 03
2
Numeric class and sasxport.get
Dear R-users, The sasxport.get function (from the Hmisc package) automatically defines the class of imported variables. I have noticed that the class of theoretically numeric variables is simply "labelled", although character variables might end up been defined as "labelled" "Date" or "labelled" "factor". Is there a way to tell sasxport.get to
2005 Dec 14
0
SAS.xpt/STATA.dta, field descriptions, and dbWriteTable
Hello all, I have a large database (~100MB in 13 relational files) that made its way to me in 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.
2008 Dec 03
2
reading version 9 SAS datasets in R
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
2018 Apr 14
0
Fwd: Re: Reading xpt files into R
-------- 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
2008 Feb 25
1
Read.xport function in package foreign
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:
2013 May 01
1
foreign: write.xport
I see in the archives significant discussion about SAS, CDISC formats etc. for FDA, but no direct suggestion of adding a write.xport method to the foreign package. Are there significant barriers to doing so? [[alternative HTML version deleted]]
2005 Jul 14
3
read.xport
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)
2004 Nov 23
3
Problem with read.xport() from foreigh package (PR#7389)
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
2004 Jun 04
0
New versions of Hmisc and Design on CRAN
New versions of source packages for Hmisc and Design are available from CRAN for R 1.9 on Linux/Unix. Knowing Uwe Ligges, a Windows binary is not far behind. Changelogs are at http://biostat.mc.vanderbilt.edu/twiki/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