<?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: Exporting multiple SAS datasets to XML creating a unique &amp;lt;table&amp;gt; container in Mathematical Optimization, Discrete-Event Simulation, and OR</title>
    <link>https://communities.sas.com/t5/Mathematical-Optimization/Exporting-multiple-SAS-datasets-to-XML-creating-a-unique-lt/m-p/39531#M345</link>
    <description>Hi:&lt;BR /&gt;
  Unless you REALLY need the libname engine, I would recommend that you use the ExcelXP destination to create your files. That's because ExcelXP writes the kind of XML that Excel "likes" -- Microsoft came up with Spreadsheet Markup Language XML in Office 2002/2003 and ODS has been able to create this specific kind of XML since SAS 9 first came out.&lt;BR /&gt;
&lt;BR /&gt;
  If you use the LIBNAME engine, you get "generic" tabular XML -- and, as you have discovered, Excel may or may not be happy with that form of XML. The only way to change the &amp;lt;TABLE&amp;gt; tag is to modfy the tagset template definition using PROC TEMPLATE.&lt;BR /&gt;
&lt;BR /&gt;
I recommend that you try this:&lt;BR /&gt;
&lt;BR /&gt;
[pre]&lt;BR /&gt;
ods tagsets.excelxp file='f:\myxml\xml1.xml' style=sasweb;&lt;BR /&gt;
  proc print data=lib.file1;&lt;BR /&gt;
  run;&lt;BR /&gt;
ods tagsets.excelxp close;&lt;BR /&gt;
          &lt;BR /&gt;
ods tagsets.excelxp file='f:\myxml\xml2.xml' style=sasweb;&lt;BR /&gt;
  proc print data=lib.file2;&lt;BR /&gt;
  run;&lt;BR /&gt;
ods tagsets.excelxp close;&lt;BR /&gt;
[/pre]&lt;BR /&gt;
   &lt;BR /&gt;
cynthia</description>
    <pubDate>Sun, 17 Aug 2008 16:21:28 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2008-08-17T16:21:28Z</dc:date>
    <item>
      <title>Exporting multiple SAS datasets to XML creating a unique &lt;table&gt; container</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Exporting-multiple-SAS-datasets-to-XML-creating-a-unique-lt/m-p/39530#M344</link>
      <description>I hope someone can help me. I am endeavoring to output a number of SAS datasets to XML using the following example libname statements&lt;BR /&gt;
&lt;BR /&gt;
libname xml1 xml "f:\xml\myxml\xml1.xml";&lt;BR /&gt;
libname xml2 xml "f:\xml\myxml\xml2.xml";&lt;BR /&gt;
and so on ....&lt;BR /&gt;
libname xml9 xml "f:\xml\myxml\xml9.xml";&lt;BR /&gt;
&lt;BR /&gt;
I then attempt to read the XML documents created into EXCEL 2007.  My problem relates to the xml data all having the outer container being called &lt;TABLE&gt; How do I get around this problem ?&lt;BR /&gt;
&lt;BR /&gt;
David&lt;/TABLE&gt;</description>
      <pubDate>Sun, 17 Aug 2008 13:01:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Exporting-multiple-SAS-datasets-to-XML-creating-a-unique-lt/m-p/39530#M344</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-08-17T13:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: Exporting multiple SAS datasets to XML creating a unique &lt;table&gt; container</title>
      <link>https://communities.sas.com/t5/Mathematical-Optimization/Exporting-multiple-SAS-datasets-to-XML-creating-a-unique-lt/m-p/39531#M345</link>
      <description>Hi:&lt;BR /&gt;
  Unless you REALLY need the libname engine, I would recommend that you use the ExcelXP destination to create your files. That's because ExcelXP writes the kind of XML that Excel "likes" -- Microsoft came up with Spreadsheet Markup Language XML in Office 2002/2003 and ODS has been able to create this specific kind of XML since SAS 9 first came out.&lt;BR /&gt;
&lt;BR /&gt;
  If you use the LIBNAME engine, you get "generic" tabular XML -- and, as you have discovered, Excel may or may not be happy with that form of XML. The only way to change the &amp;lt;TABLE&amp;gt; tag is to modfy the tagset template definition using PROC TEMPLATE.&lt;BR /&gt;
&lt;BR /&gt;
I recommend that you try this:&lt;BR /&gt;
&lt;BR /&gt;
[pre]&lt;BR /&gt;
ods tagsets.excelxp file='f:\myxml\xml1.xml' style=sasweb;&lt;BR /&gt;
  proc print data=lib.file1;&lt;BR /&gt;
  run;&lt;BR /&gt;
ods tagsets.excelxp close;&lt;BR /&gt;
          &lt;BR /&gt;
ods tagsets.excelxp file='f:\myxml\xml2.xml' style=sasweb;&lt;BR /&gt;
  proc print data=lib.file2;&lt;BR /&gt;
  run;&lt;BR /&gt;
ods tagsets.excelxp close;&lt;BR /&gt;
[/pre]&lt;BR /&gt;
   &lt;BR /&gt;
cynthia</description>
      <pubDate>Sun, 17 Aug 2008 16:21:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Mathematical-Optimization/Exporting-multiple-SAS-datasets-to-XML-creating-a-unique-lt/m-p/39531#M345</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2008-08-17T16:21:28Z</dc:date>
    </item>
  </channel>
</rss>

