Date: Thu, 21 Feb 2008 10:11:18 -0500
Reply-To: Jim Agnew <agnew@VCU.EDU>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jim Agnew <agnew@VCU.EDU>
Subject: Re: Error with Proc IMPORT
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I sympathize... we have some medical data we can't normalize easily...
it logically stays together... Data_Null_ is right in most cases, tho.
> Actually, it is STILL 256 in Access 2007...Microsoft does not seem to understand that all the gene people have thousands and thousands of variables...
> ----- Original Message -----
> From: Jim Agnew
> To: SAS-L@LISTSERV.UGA.EDU
> Sent: Wednesday, February 20, 2008 2:47 PM
> Subject: Re: Error with Proc IMPORT
> Probably what it USED to be.. that limit in old Access 2000 was what
> drove us to MySQL, plus one can use the MySQL migration wizard to
> migrate not only data but schemas from access to Mysql...
> one gotcha.... it will recode the yes/no values...
> Frank Mwaniki wrote:
> > <I followed what Mr. Nat Wooding said, saved the excel file as a csv
> > file,
> > then used proc import, and succeeded. I also called SAS help and they
> > said
> > it is a problem of Microsoft; Excel can not have more than 256 columns.>
> > Actually, Excel 2007 can handle 16,384 columns (256*64). Go figure.
> > Frank
> "Games? Solitaire? I have a 2-node VAXcluster, 2 Windows 2000 servers, 1
> Windows 2003 server, 1 MySQL server, 1 Linux server, several Ubuntus and
> a direct satellite feed to my windows desktop background, who needs
> toys???" - Jim
"Games? Solitaire? I have a 2-node VAXcluster, 2 Windows 2000 servers, 1
Windows 2003 server, 1 MySQL server, 1 Linux server, several Ubuntus and
a direct satellite feed to my windows desktop background, who needs
toys???" - Jim