similar to: foreign::read.ssd and long names (PR#9631)

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) When I filed this a few minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member

I'm trying to read in a sas system file (.sas7bdat) created under SAS 8.2 using read.ssd as follows: > library(foreign) > libname <- "c:/sasuser/consult/" > sascmd <- "c:/Program\ Files/SAS\ Institute/SAS/V8/sas.exe" > subset <- read.ssd(libname, "subset", sascmd=sascmd) SAS failed. SAS program at c:\windows\TEMP\Rtmp6673\file24544.sas a

Full_Name: Jeff Hallman Version: 2.0 OS: Linux Submission from: (NULL) (132.200.32.34) The function findGeneric() in the utils namespace contains this internal function: isUME <- function(e) { if (is.call(e) && (is.name(e[[1]]) || is.character(e[[1]]))) { switch(as.character(e[[1]]), UseMethod = as.character(e[[2]]), "{" =

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

Full_Name: Jeff Hallman Version: 2.3.1 OS: Windows Submission from: (NULL) (132.200.32.34) Internal(format.POSIXlt(as.POSIXlt(Sys.time()), "%Y%m%d%q", F)) Linux R-2.2.1 returns "20060613%q". Windows R-2.3.1 returns "20060613" dropping the "%q". The documentation says "Any character in the format string other that the '%' escape

Jeffrey J. Hallman wrote: >OK, I looked at the documentation and you're right about that. However, >I'm curious about why the first argument to UseMethod is ever necessary. >Is there ever a good reason for it to be something other than the name >of the calling function? (Wouldn't that lead to confusing code?) If >not, why bother with it at all? > >I've

>>>>> "Stephen" == Stephen Arthur <sarthur67 at yahoo.com> writes: Stephen> The SAS data set I PROC CPORTed is [9] the result is [10]. Stephen> I PROC CIMPORTed [10] back to its orginal state [9], and it Stephen> worked. Stephen> So the SAS people think that the error is not with the SAS Stephen> XPORT file, but with R trying to load a text

On Tue, 13 Jun 2006, jhallman at frb.gov wrote: > Full_Name: Jeff Hallman > Version: 2.3.1 > OS: Windows > Submission from: (NULL) (132.200.32.34) > > > Internal(format.POSIXlt(as.POSIXlt(Sys.time()), "%Y%m%d%q", F)) > Linux R-2.2.1 returns "20060613%q". > Windows R-2.3.1 returns "20060613" dropping the "%q". There is no

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

Hello, I'm trying to import a SAS file made using SAS on Unix. Currently I'm using SAS on Windows and I'm trying to import that .ssd04 file to R. The file name of the file is testfile.ssd04 and it is located in 'M:\sasuser'. I'm using Windows XP and R 2.91. Basically what I'm doing is ############ r code ############## > library(foreign) > sashome <-

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:

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,

Dear all, First of all, I thank you for the creation of the package. I write this message concerning the write.foreign() function from the foreign package and a bug that I discovered. When we want to save our dataset as a .sas file, the limit of variable names character is 8 by default. In SAS this limit is 32 character and an argument in the function, validvarname, can theorically switch the

I have downloaded R--no problem there. Unfortunately, I have run into a second problem. I am trying to use read.ssd and then read.xport (to get a SAS data set). I have imported the package "foreign" according to instructions ( options(CRAN="http://cran.us.r-project.org/") and install.packages("foreign") ), but when I do so and then use either read.ssd or read.xport I

Did not seem to reach Saikat DebRoy, this might be the forum. Bendix -----Original Message----- From: BXC (Bendix Carstensen) Sent: 24. november 2008 15:00 To: 'saikat at stat.wisc.edu'; 'stvjc at channing.harvard.edu' Subject: read.ssd It's always annoyed me that that read.ssd crashed on datasets with long variable names, but the other day a collegue of mine pointed out to

My question is about the write.foreign() command in the foreign package. I use a command like the following to try and output data and a code file to read my data into SAS. write.foreign(data.frame.object, datafile="filepath", codefile="filepath", package="SAS", dataname="myData") With my data set, it gives the following error: Error in

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,

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

Under platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 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

Full_Name: Jeff Hallman Version: 1.2.2 OS: Solaris Submission from: (NULL) (132.200.32.33) "boink<-" <- function(x, a = 1, b = 2, value){ print(match.call()) x } > z <- 1 > boink(z, b = 4) <- 22 boink<-(x = *tmp*, a = 4, value = 22) > Shouldn't it have matched the 4 to b, not a?