Date: Tue, 21 Jul 2009 13:04:36 -0500
Reply-To: Joe Matise <snoopy369@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Joe Matise <snoopy369@GMAIL.COM>
Subject: Re: SAS 9.2 Import/Export From/To MS Office 2007
Content-Type: text/plain; charset=ISO-8859-1
With the same version I see xlsx options. The dropdown says
Select a data source from the list below:
Microsoft Excel Workbook (*.xls, *.xlsb, *.xlsm, *.xlsx)
and the dropdown in the Browse... menu has each of these four as a separate
option. [SAS: Please change that to being all four at once - no reason to
have them split out like that. Yes, you should know which one you're
pulling in, but it's another unnecessary click.]
I'm on XP 5.1 also. I assume he definitely has 2007 installed on that
Also, does PROC IMPORT and/or libname access work? They should. If one
works but not the import wizard, maybe something's funny with your install.
Since it uses the ACE, which is part of Office 2007, I'd wonder if it might
have trouble seeing that? Or if Excel2007 is a separate license or
On Tue, Jul 21, 2009 at 12:50 PM, Michael Raithel <email@example.com
> Dear SAS-L-ers,
> Here at SAS Mecca, we are just starting to migrate some "Early Adopters"
> from SAS 9.1.3 to SAS 9.2 TS2M0 on Windows XP Version 5.1 (and other
> platforms that are not relevant to this post).
> One of our Early Adopters just reported that in Windows SAS Display
> Manager, when selecting either
> <File> <Import Data>, or
> <File> <Export Data>,
> ...none of the Microsoft Office 2007 products are rendered as choices in
> the "Select a data source from the list below" drop down window. For
> example, the first choice is "Microsoft Excel 97/2000/2002/2003 Workbook".
> This is vexing because our SAS Early Adopter is also one of our MS Office
> 2007 Early Adopters and would like to use the SAS interface to import/export
> Office 2007 data the same way that he did with earlier versions.
> So, has anybody else on the 'L run into this _AND_ have a solution?
> Or, have you run into this and have implemented a workaround?
> Or, are we just on the bleeding edge of technology?!?!? (Not very likely)!
> Thank you, in advance, for your input!
> Best of luck in all of your SAS endeavors!
> I hope that this suggestion proves helpful now, and in the future!
> Of course, all of these opinions and insights are my own, and do not
> reflect those of my organization or my associates. All SAS code and/or
> methodologies specified in this posting are for illustrative purposes only
> and no warranty is stated or implied as to their accuracy or applicability.
> People deciding to use information in this posting do so at their own risk.
> Michael A. Raithel
> "The man who wrote the book on performance"
> E-mail: MichaelRaithel@westat.com
> Author: Tuning SAS Applications in the MVS Environment
> Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second
> Author: The Complete Guide to SAS Indexes
> Ancient Rome declined because it had a Senate; now what's going to
> happen to us with both a Senate and a House? - Will Rogers