Date:         Thu, 26 Jun 2008 18:51:45 -0400
Reply-To:     Arthur Tabachneck <art297@NETSCAPE.NET>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Arthur Tabachneck <art297@NETSCAPE.NET>
Subject:      Bug in Excel Import (was Converting a very large spreadsheet)
Comments: To: Paul Thompson <paul@WUBIOS.WUSTL.EDU>

While Paul informed me (offline) that he already found a way around his
problem, I did a minor test to see if I could identify what the
limitations might be (using Excel 2003 and SAS 9.1.3 in a Windows server
environment.

Excel lets me build a fully populated 256 column by 65,536 row worksheet.

SAS Proc Import says that the file doesn't exist, while using the libname
method, the libname is assigned, but the file again is said not to exist.

Interestingly, removing one column from the worksheet (i.e., making it 255
columns by 65,536 rows), proc import had no problem and only took 35
seconds to import.

Regardless of whether it is a bug or limitation, I'd be careful to avoid
using Excel's 256th column.

Art
---------
solved his problemOn Thu, 26 Jun 2008 15:49:27 -0500, Paul A. Thompson
<paul@WUBIOS.WUSTL.EDU> wrote:

>I am trying to convert a large spreadsheet from excel to SAS.  Using PC
SAS
>with PROC IMPORT, I am going on 20 minutes.  Using dbmscopy, I get a
>segmentation violation.  Any other suggestions?
>
>
>
>Paul A. Thompson, Ph.D.
>
>Division of Biostatistics, Washington University School of Medicine
>
>660 S. Euclid, St. Louis, MO 63110-1093
>
>314-747-3793
>
>paul@wubios.wustl.edu