Date: Wed, 10 Dec 2008 11:46:39 -0500
Reply-To: "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2@CDC.GOV>
Subject: Re: FYI - 64-bit nuance of Proc Export
Content-Type: text/plain; charset=us-ascii
welcome back, dude!
this is a known problem with Win x64:
that it cannot handle Excel files.
The short, condensed, response from Tech Support is:
means less native Windows apps."
Q: can you run Excel under Vista 64?
Ron Fehd the macro maven CDC Atlanta GA USA RJF2 at cdc dot gov
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of William W.
> Sent: Tuesday, December 09, 2008 8:33 PM
> To: firstname.lastname@example.org
> Subject: FYI - 64-bit nuance of Proc Export
> dudes & dudettes:
> although i've had it installed on my 64-bit Vista laptop for months, i
> just got around to installing 64-bit SAS v9.2 on my XP x64
> then, later today
> ran a job that ends w/ a Proc Export to a new Excel file
> in my Proc Export code
> DBMS = EXCEL2000 generated an error
> ditto for DBMS = EXCEL2003, and for plain ole = EXCEL
> searching through the Proc Export docs, i noticed a really-fine-print
> comment that the = EXCEL???? identifiers only hold for libname access
> so ... i then tried DBMS = XLS and
> voila! ... all is cool
> so ... inquiring minds wann know:
> is the fact that = EXCEL worked under 32-bit SAS a quirk, or did they
> do something new/diff in 64-bit SAS?
> ciao' for now,