<?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: A Poor/Rich SAS Users Proc Export in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836922#M330922</link>
    <description>That's where I started. It refers to the missing wiki link.&lt;BR /&gt;&lt;BR /&gt;WHERE TO GET THE MACRO&lt;BR /&gt;We did our best to only include carefully written and tested code, but the code may have to be updated from time to&lt;BR /&gt;time to correct for errors or enhancements that we or others might discover. Additionally, while a copy of the macro is&lt;BR /&gt;included in this paper, copying and pasting from a pdf file often introduces stylish looking quotation marks which&lt;BR /&gt;aren’t correctly recognized by SAS. As such, we created a page for the paper on sasCommunity.org. The page&lt;BR /&gt;includes copies of the source code and updated versions of this paper. The page can be found at:&lt;BR /&gt;&lt;A href="http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export" target="_blank"&gt;http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export&lt;/A&gt;</description>
    <pubDate>Wed, 05 Oct 2022 12:17:00 GMT</pubDate>
    <dc:creator>tomvincent</dc:creator>
    <dc:date>2022-10-05T12:17:00Z</dc:date>
    <item>
      <title>A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836918#M330919</link>
      <description>&lt;P&gt;Anyone know what happened to that?&amp;nbsp; it used to be at&amp;nbsp;&lt;A href="http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export" target="_blank" rel="noopener"&gt;http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export&lt;/A&gt;&amp;nbsp;but that's a dead link.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't know if it would work on Linux but I'm willing to try.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 12:06:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836918#M330919</guid>
      <dc:creator>tomvincent</dc:creator>
      <dc:date>2022-10-05T12:06:59Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836919#M330920</link>
      <description>&lt;P&gt;You can find the "&lt;A href="https://support.sas.com/resources/papers/proceedings14/1793-2014.pdf" target="_blank" rel="noopener"&gt;A Poor/Rich SAS User’s Proc Export&lt;/A&gt;" paper at&amp;nbsp;&lt;A href="https://support.sas.com/resources/papers/proceedings14/1793-2014.pdf" target="_blank"&gt;1793-2014.pdf (sas.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;May the SAS be with you &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Mark&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 12:13:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836919#M330920</guid>
      <dc:creator>SASJedi</dc:creator>
      <dc:date>2022-10-05T12:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836922#M330922</link>
      <description>That's where I started. It refers to the missing wiki link.&lt;BR /&gt;&lt;BR /&gt;WHERE TO GET THE MACRO&lt;BR /&gt;We did our best to only include carefully written and tested code, but the code may have to be updated from time to&lt;BR /&gt;time to correct for errors or enhancements that we or others might discover. Additionally, while a copy of the macro is&lt;BR /&gt;included in this paper, copying and pasting from a pdf file often introduces stylish looking quotation marks which&lt;BR /&gt;aren’t correctly recognized by SAS. As such, we created a page for the paper on sasCommunity.org. The page&lt;BR /&gt;includes copies of the source code and updated versions of this paper. The page can be found at:&lt;BR /&gt;&lt;A href="http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export" target="_blank"&gt;http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export&lt;/A&gt;</description>
      <pubDate>Wed, 05 Oct 2022 12:17:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836922#M330922</guid>
      <dc:creator>tomvincent</dc:creator>
      <dc:date>2022-10-05T12:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836927#M330923</link>
      <description>&lt;P&gt;So, then, this is probably most of what you're looking for:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/art297/Papers/blob/master/Excelling_to_Another_Level_with_SAS/src/exportxl.sas" target="_blank"&gt;Papers/exportxl.sas at master · art297/Papers (github.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 12:21:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836927#M330923</guid>
      <dc:creator>SASJedi</dc:creator>
      <dc:date>2022-10-05T12:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836931#M330925</link>
      <description>that looks more promising...I'll give that a try...thanks.&lt;BR /&gt;&lt;BR /&gt;I wonder what happened to that wiki site and why it was nuked... &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;</description>
      <pubDate>Wed, 05 Oct 2022 12:28:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836931#M330925</guid>
      <dc:creator>tomvincent</dc:creator>
      <dc:date>2022-10-05T12:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836940#M330928</link>
      <description>&lt;P&gt;I forget the reason, but sascommunity.org was nuked several years ago.&amp;nbsp; There was an effort to migrate much of the content here to articles, but not sure how successful that was.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 13:02:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836940#M330928</guid>
      <dc:creator>Quentin</dc:creator>
      <dc:date>2022-10-05T13:02:54Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836941#M330929</link>
      <description>I ***HATE*** when companies do that. They should just keep the old pages and set them to read-only. grrr...</description>
      <pubDate>Wed, 05 Oct 2022 13:06:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836941#M330929</guid>
      <dc:creator>tomvincent</dc:creator>
      <dc:date>2022-10-05T13:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836943#M330930</link>
      <description>&lt;P&gt;Working with the volunteer team that managed sasCommunity.org, we moved most of the unique/popular content to this community site and decommissioned the sasCommunity.org site. It was hosted on a 3rd-party platform -- which has a cost in both fees and people to manage. The traffic had reduced considerably, especially after much of the content moved here. It was a long process but all those involved agreed it was the right time to do this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;More information &lt;A href="https://communities.sas.com/t5/SAS-Programming/Updated-exportxl-macro-now-available/m-p/191357" target="_self"&gt;about exportxl is here&lt;/A&gt;. I reviewed the code recently and I think it relies on SAS code to generate VB Script to automate Excel. Effective method, but that won't work on its own on Linux.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We usually recommend ODS Excel to people who need more control over the Excel documents they create: formatting, formulas, etc. However ODS Excel always creates a new workbook file, and cannot update existing spreadsheets.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One possible approach&amp;nbsp;(which I have &lt;STRONG&gt;not&lt;/STRONG&gt; tried) in SAS Viya is to use the &lt;A href="https://openpyxl.readthedocs.io/en/stable/" target="_blank"&gt;Python library called OpenPyXL&lt;/A&gt;. You would add this Python library to the Python installation where SAS Viya runs, and then use PROC PYTHON to alter the Excel file with Python code. You could use SAS to generate the values you need, then PROC PYTHON to drive those values into a spreadsheet file, and then publish/download the Excel file where you need it.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 13:21:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836943#M330930</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2022-10-05T13:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836957#M330939</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/366437"&gt;@tomvincent&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;I ***HATE*** when companies do that. They should just keep the old pages and set them to read-only. grrr...&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;It wasn't company managed, people managed aka open source.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 14:31:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836957#M330939</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2022-10-05T14:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836969#M330942</link>
      <description>Thanks, Chris. I think a better solution would have been to host the archive of sascommunity.org within the communities.sas.com website...no cost to manage at all.&lt;BR /&gt;&lt;BR /&gt;I think I suggested years ago that SAS have the ability to write to a range (since it can *read* from one)...maybe fix that damned white space bug at the same time...:(</description>
      <pubDate>Wed, 05 Oct 2022 14:47:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/836969#M330942</guid>
      <dc:creator>tomvincent</dc:creator>
      <dc:date>2022-10-05T14:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: A Poor/Rich SAS Users Proc Export</title>
      <link>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/847769#M335167</link>
      <description>Even worse. Unlike the 'supreme' court, I'm convinced that companies are comprised of people.</description>
      <pubDate>Mon, 05 Dec 2022 12:55:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/A-Poor-Rich-SAS-Users-Proc-Export/m-p/847769#M335167</guid>
      <dc:creator>tomvincent</dc:creator>
      <dc:date>2022-12-05T12:55:40Z</dc:date>
    </item>
  </channel>
</rss>

