search for: validvarnam

...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 default from 8 to 32 by selecting validvarname = "V7". However, it did not work and show the error "Cannot uniquely abbreviate format names to conform to eight-character limit and not ending in a digit" that show the limit is still 8 characters. By...

...ote <- function (x) paste("\"", x, "\"", sep = "") dfile <- file.path(tempdir(), "test.dat") cfile <- file.path(tempdir(), "test.sas") write.foreign(d, datafile = dfile, codefile = cfile, package = "SAS7", validvarname = "V6") file.show(dfile) file.show(cfile) Sincerely, Stephen :::::::::::::::::::::::::::::::::: Stephen Weigand Division of Biostatistics Mayo Clinic Rochester, Minn., USA Phone (507) 266-1650, fax 284-9542 -------------- next part -------------- --- writeForeignSAS.R Fri Feb 17...

...ry 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 make.SAS.names(names(df), validvarname = validvarname) : Cannot uniquely abbreviate the variable names to 32 or fewer characters I tried to write reproducible code but could not. I'm not sure where to go from here. What are the naming protocols for variables so that they can be exported using write.foreign()? Thanks!...

...d() 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 of the columns in the dataset being copied are too long, unless you first set (in SAS) "option validvarname = v6;". I'm including here a rewritten read.ssd() that deals with these two issues. The sectionnames 8-character limitation is dealt with by creating symbolic links with shorter names. The problem with long column names is handled by adding SAS code to set "option validvarname =...

...rent directory NULL Warning message: In read.ssd(folder_for_datafiles, "testfile", sascmd = file.path(sashome, : SAS return code was 2 > ################################## This temporary SAS file 'file41bb5af1.sas' looks like this ############ sas code ############# option validvarname = v6;libname src2rd 'M:/sasuser'; libname rd xport 'C:\DOCUME~1\jrara\LOCALS~1\Temp\RtmpAAxO3X\file6df11649'; proc copy in=src2rd out=rd; select testfile ; ################################## Any ideas what I'm doing wrong? > sessionInfo() R version 2.9.1 (2009-06-26) i386...

...subset<- read.xport("c:/sasuser/consult/subset.xport") However, I encountered problems in SAS which might need to be taken into account in read.ssd. Under SAS V8, variable names can be up to 32 characters, but the PROC COPY (which is used in read.ssd will fail, unless the SAS option, validvarname=V6 is used, as in: libname rd 'c:\sasuser\consult'; libname subset xport "c:\sasuser\consult\subset.xport"; options validvarname=v6; proc copy in=rd out=subset; select subset; run; -Michael -- Michael Friendly friendly at yorku.ca York University...

...d() 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 of the columns in the dataset being copied are too long, unless you first set (in SAS) "option validvarname = v6;". I'm including here a rewritten read.ssd() that deals with these two issues. The sectionnames 8-character limitation is dealt with by creating symbolic links with shorter names. The problem with long column names is handled by adding SAS code to set "option validvarname =...

...tensen) 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 me the SAS-option validvarname=V6, which takes care of the problem by truncating names. So here is a first go at it which works, but lets you guess what variable the truncated names refer to (normally a minor problem). The small changes in the code are flagged with "####". Hope it makes it into read.ssd. If you want...

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