<?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: SAs 9.3 and upgrade to office 2016 from office 2010 in Microsoft Integration with SAS</title>
    <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342150#M2024</link>
    <description>&lt;P&gt;ODS TAGSETS.EXCELXP and ODS HTML3 are independent of any Microsoft shenanigans, so they should not be affected.&lt;/P&gt;
&lt;P&gt;When using ACCESS to PC Files for pre-xlsx formats, bitness might be an issue. Make sure that SAS and Office have the same bitness.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Mar 2017 20:32:55 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2017-03-17T20:32:55Z</dc:date>
    <item>
      <title>SAs 9.3 and upgrade to office 2016 from office 2010</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342118#M2023</link>
      <description>&lt;P&gt;We use SAS 9.3.1 64-bit on Windows 7Pro, and integrate with MS office 2010 Excel through Access PC files and SAS ODS HTML3 or ODS TAGSETS.EXCEXP.&amp;nbsp; IT will move us to Office 2016/365.&amp;nbsp; Does sas 9.3.1 support office 2016? I have received conflicting information. Do we need to get any additional software short of upgrading to SAS 9.4 to be able to interface with Excel?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Mar 2017 19:09:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342118#M2023</guid>
      <dc:creator>khsundet</dc:creator>
      <dc:date>2017-03-17T19:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: SAs 9.3 and upgrade to office 2016 from office 2010</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342150#M2024</link>
      <description>&lt;P&gt;ODS TAGSETS.EXCELXP and ODS HTML3 are independent of any Microsoft shenanigans, so they should not be affected.&lt;/P&gt;
&lt;P&gt;When using ACCESS to PC Files for pre-xlsx formats, bitness might be an issue. Make sure that SAS and Office have the same bitness.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Mar 2017 20:32:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342150#M2024</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-03-17T20:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: SAs 9.3 and upgrade to office 2016 from office 2010</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342154#M2025</link>
      <description>&lt;P&gt;Thank you for your reply. We use xlsx files, so the bitness should not be an issue but I'll definitely ask for 64-bit to be sure of compatibility with SAS and WIN 7.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Mar 2017 20:45:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/SAs-9-3-and-upgrade-to-office-2016-from-office-2010/m-p/342154#M2025</guid>
      <dc:creator>khsundet</dc:creator>
      <dc:date>2017-03-17T20:45:15Z</dc:date>
    </item>
  </channel>
</rss>

