<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Excel2007 in Microsoft Integration with SAS</title>
    <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4847#M180</link>
    <description>Sorry I was not clear.&lt;BR /&gt;
&lt;BR /&gt;
I created 235 files with the external application, and I use SAS proc import to import them.&lt;BR /&gt;
But on the PC, with have MSO2007 so the files generated were with the Excel 2007 format (because the application uses MS-Jet Engine installed on the PC to create them) , so the proc import can't work.&lt;BR /&gt;
The XLSX is a XML compressed format, in reality.&lt;BR /&gt;
&lt;BR /&gt;
The solution is to use OLE DB engine to read these files or save them in .txt format.&lt;BR /&gt;
&lt;BR /&gt;
As always, thanks Cynthia.</description>
    <pubDate>Thu, 27 Sep 2007 09:16:27 GMT</pubDate>
    <dc:creator>Stephane</dc:creator>
    <dc:date>2007-09-27T09:16:27Z</dc:date>
    <item>
      <title>Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4842#M175</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
we use SAS 9.1.3 SP4 and use Access to PC files for many times.&lt;BR /&gt;
&lt;BR /&gt;
We've just installed Office 2007 and the MS-Jet that goes with.&lt;BR /&gt;
&lt;BR /&gt;
Before, I created excel files with an external application and I imported the results into SAS with a proc Import Dbms=Excel2002. goes fine.&lt;BR /&gt;
&lt;BR /&gt;
Now, when I execute the Proc Import, SAS writes "Connect: External table is not in the expected format"&lt;BR /&gt;
&lt;BR /&gt;
=&amp;gt; Why ??</description>
      <pubDate>Wed, 26 Sep 2007 14:48:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4842#M175</guid>
      <dc:creator>Stephane</dc:creator>
      <dc:date>2007-09-26T14:48:46Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4843#M176</link>
      <description>I'm sorry to be the bearer of bad news:&lt;BR /&gt;
&lt;A href="http://support.sas.com/techsup/unotes/SN/019/019550.html" target="_blank"&gt;http://support.sas.com/techsup/unotes/SN/019/019550.html&lt;/A&gt;</description>
      <pubDate>Wed, 26 Sep 2007 16:09:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4843#M176</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2007-09-26T16:09:36Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4844#M177</link>
      <description>If you have the SAS Add-in for Microsoft Office and the whole Enterprise Intelligence Platform, then it is true that the SAS Add-in does not yet work with Office 2007.&lt;BR /&gt;
&lt;BR /&gt;
PROC IMPORT and PROC EXPORT can handle things a bit differently -- but it takes a bit of work. Importing Excel 2007 format may be problematic because in Office 2007, by default, Excel 2007, saves your Excel files as XML -- the new Microsoft format for Excel and uses a file extension of .XLSX -- I do not know when PROC IMPORT and/or PROC EXPORT will be able to read this new format.&lt;BR /&gt;
&lt;BR /&gt;
However, you can SAVE your Excel spreadsheet (in Office 2007) to a "back-level" of Excel (I believe the button says Save as Excel97-2003 format)  -- if you save as that older format, then your PROC IMPORT should still work. (Just as if you EXPORT using an older format, then Excel will still open the older format file.)&lt;BR /&gt;
&lt;BR /&gt;
For more help, with PROC IMPORT, you might with to contact SAS Tech Support.&lt;BR /&gt;
 &lt;A href="http://support.sas.com/techsup/contact/index.html" target="_blank"&gt;http://support.sas.com/techsup/contact/index.html&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
cynthia</description>
      <pubDate>Wed, 26 Sep 2007 17:17:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4844#M177</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2007-09-26T17:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4845#M178</link>
      <description>thank you.&lt;BR /&gt;
&lt;BR /&gt;
In fact I create 235 files with an application that doesn't allow to create a back-level of Excel&lt;BR /&gt;
&lt;BR /&gt;
But I'm surprised. In fact, when I open the xls file with notepad it appears like a binay file and not a XML file. &lt;BR /&gt;
If the files are in XML, do i can open them with notepad or perhaps IE and see a XML document ?&lt;BR /&gt;
&lt;BR /&gt;
By this question, I'm wondering if the MS-Jet Engine of Office 2007 can create a true Excel 2007.</description>
      <pubDate>Wed, 26 Sep 2007 19:16:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4845#M178</guid>
      <dc:creator>Stephane</dc:creator>
      <dc:date>2007-09-26T19:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4846#M179</link>
      <description>Hi:&lt;BR /&gt;
  Honestly, this is a question for Tech Support. I don't know what happens if you create 235 files automatically -- are you using PROC EXPORT for this task? I did not think that SAS would create Office/Excel 2007 files yet with PROC EXPORT.&lt;BR /&gt;
&lt;BR /&gt;
 I thought your question was with IMPORTing the files back into SAS. At any rate, when I use Office/Excel 2007 to create 1 file, by opening Excel and typing into the application and then doing a FILE--&amp;gt;SAVE As Excel automatically wants to name the file with a .XLSX extension. It was my understanding that the XLSX was the "new" format and was some hybrid of Excel and XML markup format -- that was proprietary to Microsoft. It is NOT the same as Spreadsheet Markup Language XML that was the Office 2002/2003 XML.&lt;BR /&gt;
 &lt;BR /&gt;
If you cannot save your Excel files to a "back-level" then Tech Support will have to answer your question about whether PROC IMPORT (or PROC EXPORT) will be able to read and write Excel 2007 files.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Wed, 26 Sep 2007 22:16:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4846#M179</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2007-09-26T22:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4847#M180</link>
      <description>Sorry I was not clear.&lt;BR /&gt;
&lt;BR /&gt;
I created 235 files with the external application, and I use SAS proc import to import them.&lt;BR /&gt;
But on the PC, with have MSO2007 so the files generated were with the Excel 2007 format (because the application uses MS-Jet Engine installed on the PC to create them) , so the proc import can't work.&lt;BR /&gt;
The XLSX is a XML compressed format, in reality.&lt;BR /&gt;
&lt;BR /&gt;
The solution is to use OLE DB engine to read these files or save them in .txt format.&lt;BR /&gt;
&lt;BR /&gt;
As always, thanks Cynthia.</description>
      <pubDate>Thu, 27 Sep 2007 09:16:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4847#M180</guid>
      <dc:creator>Stephane</dc:creator>
      <dc:date>2007-09-27T09:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4848#M181</link>
      <description>Ah, got it! That makes sense.&lt;BR /&gt;
 &lt;BR /&gt;
You could also save your 235 files as .CSV files instead of .TXT and then you'd be able to read them with SAS.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Thu, 27 Sep 2007 15:58:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4848#M181</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2007-09-27T15:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4849#M182</link>
      <description>Just a thought.&lt;BR /&gt;
&lt;BR /&gt;
Could you programmatically loop through the spreadsheets using SAS and DDE (or an Excel macro) to open the spreadsheets and "re-save" them as XLS 97-2003 spreadsheets?</description>
      <pubDate>Tue, 02 Oct 2007 16:34:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4849#M182</guid>
      <dc:creator>advoss</dc:creator>
      <dc:date>2007-10-02T16:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4850#M183</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
I face the same problem and I was wondering if it's now (5 months later) possible to use the proc import with an .XLSX file ?&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance,&lt;BR /&gt;
Florent</description>
      <pubDate>Mon, 03 Mar 2008 11:27:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4850#M183</guid>
      <dc:creator>Florent</dc:creator>
      <dc:date>2008-03-03T11:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4851#M184</link>
      <description>Hi, Florent:&lt;BR /&gt;
  To learn what an XLSX file really is, create a file with Excel 2007 and save it with the default .XLSX name.&lt;BR /&gt;
&lt;BR /&gt;
  Then, go to Windows Explorer, find the file where you saved it and RENAME the file extension to .ZIP -- then open the zip file with WinZip. Or, open WinZip first then then choose open from inside WinZip and navigate to where you saved the .XLSX file -- WinZip opened it very nicely and then you can view the XML files inside the archive using NOTEPAD. Anyway, you will see that there's not just 1 file, but a group of related files -- mostly XML.&lt;BR /&gt;
&lt;BR /&gt;
Microsoft is calling this the Office Open XML format. You can see a picture of what an XLSX file really contains here:&lt;BR /&gt;
&lt;A href="http://blogs.msdn.com/excel/archive/2006/07/20/671995.aspx" target="_blank"&gt;http://blogs.msdn.com/excel/archive/2006/07/20/671995.aspx&lt;/A&gt;&lt;BR /&gt;
 &lt;BR /&gt;
  I don't actually know whether PROC IMPORT can read an XLSX file yet -- that's still a question for Tech Support. The only thing I found on searching support.sas.com on .XLSX and IMPORT was this note about EG 4.1: &lt;A href="http://support.sas.com/kb/4/484.html" target="_blank"&gt;http://support.sas.com/kb/4/484.html&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
  cynthia</description>
      <pubDate>Mon, 03 Mar 2008 16:18:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4851#M184</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2008-03-03T16:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4852#M185</link>
      <description>Thank you for the explanations.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Florent</description>
      <pubDate>Mon, 03 Mar 2008 16:29:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4852#M185</guid>
      <dc:creator>Florent</dc:creator>
      <dc:date>2008-03-03T16:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4853#M186</link>
      <description>Have you tried using ODBC to read the spreadsheet?</description>
      <pubDate>Mon, 03 Mar 2008 17:18:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4853#M186</guid>
      <dc:creator>advoss</dc:creator>
      <dc:date>2008-03-03T17:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4854#M187</link>
      <description>Yes, it works fine but the problems are that we have to update every SAS programs and we have to buy ODBC licences for every computer using these programs.</description>
      <pubDate>Tue, 04 Mar 2008 13:07:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4854#M187</guid>
      <dc:creator>Florent</dc:creator>
      <dc:date>2008-03-04T13:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4855#M188</link>
      <description>I assume SAS also realizes that XLSM is a format that needs read as well?  Macro enabled file extensions must be XLSM.</description>
      <pubDate>Tue, 17 Jun 2008 16:45:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4855#M188</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-06-17T16:45:27Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4856#M189</link>
      <description>SAS 9.2 provides native support for Excel 2007 as well as other Office 2007 file formats.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://support.sas.com/documentation/cdl/en/acpcref/61891/HTML/default/acpcrefwhatsnew902.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/acpcref/61891/HTML/default/acpcrefwhatsnew902.htm&lt;/A&gt;</description>
      <pubDate>Fri, 13 Mar 2009 07:47:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4856#M189</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-03-13T07:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4857#M190</link>
      <description>I am using SAS 9.2 Phase 2 and I am still not able to import xlsm files, even though I can import xlsx files without any problems.  This is the error message that occurs whenever I try to import an xlsm file:&lt;BR /&gt;
&lt;BR /&gt;
ERROR: Connect: External table is not in the expected format.&lt;BR /&gt;
ERROR: Error in the LIBNAME statement.&lt;BR /&gt;
Connection Failed.  See log for details.&lt;BR /&gt;
&lt;BR /&gt;
Any thoughts on this problem would be greatly appreciated.</description>
      <pubDate>Wed, 21 Jul 2010 16:59:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4857#M190</guid>
      <dc:creator>polingjw</dc:creator>
      <dc:date>2010-07-21T16:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4858#M191</link>
      <description>Hi:&lt;BR /&gt;
  The Tech Support note that Scott referenced in an earlier post in this thread talks about how you can import .XLSX files using SAS 9.2, Phase 2.&lt;BR /&gt;
 &lt;BR /&gt;
  If you think about it, an Excel "macro-enabled" spreadsheet of type .XLSM, has something above and beyond the data added to it (Excel macro instructions). I don't know whether there are any plans to be able to read .XLSM files with the LIBNAME engine or PROC IMPORT. This would be a question for Tech Support.&lt;BR /&gt;
 &lt;BR /&gt;
  If you save the .XLSM file as a .XLSX or .XLS (Excel 97-2003 file), can you then read the spreadsheet with SAS??? I would expect so.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Wed, 21 Jul 2010 23:39:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4858#M191</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2010-07-21T23:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4859#M192</link>
      <description>Yes, I can read the file when saved as a .XLS document.  The author of the file, however, wants to keep the file in the macro-enabled Excel 2007 format.  As an alternative, I was able to read the data using DDE.&lt;BR /&gt;
&lt;BR /&gt;
Thanks.</description>
      <pubDate>Thu, 22 Jul 2010 16:35:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4859#M192</guid>
      <dc:creator>polingjw</dc:creator>
      <dc:date>2010-07-22T16:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: Excel2007</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4860#M193</link>
      <description>When I've encountered similar situations in the past, I've used a separate VBA process to save a new copy of the file in .xls format, before running the SAS import process. The macro-enabled copy is preserved but not read in. The issue of course is the duplication of the files.</description>
      <pubDate>Thu, 22 Jul 2010 22:07:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Excel2007/m-p/4860#M193</guid>
      <dc:creator>GeoffNess</dc:creator>
      <dc:date>2010-07-22T22:07:02Z</dc:date>
    </item>
  </channel>
</rss>

