<?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: ODS output result not displayed in Developers</title>
    <link>https://communities.sas.com/t5/Developers/ODS-output-result-not-displayed/m-p/165270#M4212</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; There have been many previous forum postings, in this forum, about using TAGSETS.EXCELXP. Generally, as a stored process, TAGSETS.EXCELXP output can only be the destination returned to a few of the client applications: the Information Delivery Portal and to a browser using the Stored Process Web App. Even Excel will not accept a stored process whose destination has been set to TAGSETS.EXCELXP. If some client applications recognize that you are using a destination that they don't accept, they will either not show you anything or show you a blank screen or sometimes, change the destination behind the scenes to SASReport XML. So without actually seeing the code you created and whether your overrode &amp;amp;_ODSDEST correctly and/or whether you set the content-type header correctly, it is hard to make more constructive suggestions except that you search the forum for postings on stored processes and TAGSETS.EXCELXP. You should find plenty of hits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 06 Apr 2014 04:24:09 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2014-04-06T04:24:09Z</dc:date>
    <item>
      <title>ODS output result not displayed</title>
      <link>https://communities.sas.com/t5/Developers/ODS-output-result-not-displayed/m-p/165269#M4211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a program that creates an output file using ODS Target.excelxp. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i run it normally in EG , i see an addtional tab of result from where I can download it. &lt;/P&gt;&lt;P&gt;However when i convert the code and run it as a stored procedure, the result tab does not appear. &lt;/P&gt;&lt;P&gt;Please see the attachment. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone faced this issue before and was able to solve it.&amp;nbsp; Is there some setting I am missing ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Smijo&lt;/P&gt;&lt;BR /&gt;&lt;IMG src="https://communities.sas.com/t5/image/serverpage/image-id/11247i6F7266CD68B711CD/image-size/large?v=1.0&amp;amp;px=600" border="0" alt="storeprocess2.JPG" title="storeprocess2.JPG" /&gt;&lt;IMG src="https://communities.sas.com/t5/image/serverpage/image-id/11248i20C9F55E5B252637/image-size/large?v=1.0&amp;amp;px=600" border="0" alt="storeprocess1.JPG" title="storeprocess1.JPG" /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Apr 2014 19:01:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Developers/ODS-output-result-not-displayed/m-p/165269#M4211</guid>
      <dc:creator>Smijoss</dc:creator>
      <dc:date>2014-04-02T19:01:48Z</dc:date>
    </item>
    <item>
      <title>Re: ODS output result not displayed</title>
      <link>https://communities.sas.com/t5/Developers/ODS-output-result-not-displayed/m-p/165270#M4212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; There have been many previous forum postings, in this forum, about using TAGSETS.EXCELXP. Generally, as a stored process, TAGSETS.EXCELXP output can only be the destination returned to a few of the client applications: the Information Delivery Portal and to a browser using the Stored Process Web App. Even Excel will not accept a stored process whose destination has been set to TAGSETS.EXCELXP. If some client applications recognize that you are using a destination that they don't accept, they will either not show you anything or show you a blank screen or sometimes, change the destination behind the scenes to SASReport XML. So without actually seeing the code you created and whether your overrode &amp;amp;_ODSDEST correctly and/or whether you set the content-type header correctly, it is hard to make more constructive suggestions except that you search the forum for postings on stored processes and TAGSETS.EXCELXP. You should find plenty of hits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 Apr 2014 04:24:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Developers/ODS-output-result-not-displayed/m-p/165270#M4212</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2014-04-06T04:24:09Z</dc:date>
    </item>
  </channel>
</rss>

