search for: validvarnames

...hat the line 39, in the function make.SAS.formats, can be the reason of the nonfunctioning argument : "if(any(nchar(x) > 8L) || any(duplicated(x)))" which is correct if the length of the variable has a limit of 8, but it does not take in consideration when the limit is at 32 defined by validvarnames = "V7". A solution can be to add the argument validvarname in the definition of the function and add these few lines : validvarname <- match.arg(validvarname) nmax <- if(validvarname == "V7") 32L else 8L if(any(nchar(x) > nmax) || any(duplicated(x))) I hope I s...

Dear R-devel, I've made some potential extensions to writeForeignSAS in 'foreign' that I wanted to pass along if anyone is interested. I've attached the diff -u output against the version found in foreign_0.8-15 and an .R file with my changes. (In this .R file, the function is named writeForeignSAS7 to simplify testing/comparisons.) I've tried to alter the current

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

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

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

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.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) 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 names (the sectionnames argument to read.ssd) longer than 8 characters. The second is that PROC COPY also fails if any

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

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