LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (September 2004, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Sat, 11 Sep 2004 01:36:34 -0400
Reply-To:   Richard Ristow <wrristow@MINDSPRING.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Richard Ristow <wrristow@MINDSPRING.COM>
Subject:   Re: SAS output: Excel or flat file?
Comments:   To: Julia Maslak <jam09@HEALTH.STATE.NY.US>
In-Reply-To:   <200409091457.i89EvW8d006102@listserv.cc.uga.edu>
Content-Type:   text/plain; charset="us-ascii"; format=flowed

Sorry -- probably naive question, but,

At 10:57 AM 9/9/2004, Julia Maslak wrote:

>I have a customer who wants me to put his output in Excel or a flat >file. I >am using PROC FREQ. I have converted *.lst output to Excel using >DBMSCopy. It's tedious.

There've been a number of suggestions how to write the .LST output to Excel.

I'd ask: why does it make any sense to do so? An Excel spreadsheet has a very definite data model, a rectangular array where each cell holds a character string, a number, or a formula computing a quantity of either type from the values of other cells.

That doesn't look like .LST output at all. I suppose you could write each line to the leftmost cell of a row in Excel; since Excel strings are displayed over as many blank cells to the right as needed, the result would look like the listing. But to what purpose? It seems to use none of Excel's capacities. What does it offer, that a .TXT file doesn't?


Back to: Top of message | Previous page | Main SAS-L page