<?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 Export protected Excel workbook using UNIX SAS in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/241909#M308987</link>
    <description>&lt;P&gt;Is anyone aware of a method for exporting an Excel file that is protected or read-only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to do this within an automated script on the UNIX server. I have seen methods that would work when using PC SAS, but they won't work on the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, I'm not concerned with having a password requirement to open the file... I just want the cells to be read-only (not able to be manipulated/deleted).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 05 Jan 2016 20:29:46 GMT</pubDate>
    <dc:creator>jweaver08</dc:creator>
    <dc:date>2016-01-05T20:29:46Z</dc:date>
    <item>
      <title>Export protected Excel workbook using UNIX SAS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/241909#M308987</link>
      <description>&lt;P&gt;Is anyone aware of a method for exporting an Excel file that is protected or read-only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to do this within an automated script on the UNIX server. I have seen methods that would work when using PC SAS, but they won't work on the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, I'm not concerned with having a password requirement to open the file... I just want the cells to be read-only (not able to be manipulated/deleted).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2016 20:29:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/241909#M308987</guid>
      <dc:creator>jweaver08</dc:creator>
      <dc:date>2016-01-05T20:29:46Z</dc:date>
    </item>
    <item>
      <title>Re: Export protected Excel workbook using UNIX SAS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/241913#M308988</link>
      <description>Unfortunately I don't think there's a way in Unix, I believe all the PC ways use the OS methods and possibly VB.</description>
      <pubDate>Tue, 05 Jan 2016 20:55:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/241913#M308988</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2016-01-05T20:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: Export protected Excel workbook using UNIX SAS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/242002#M308989</link>
      <description>&lt;P&gt;Well, there are several parts to this question. &amp;nbsp;Lets address the "why" first off. &amp;nbsp;The main use people have for using Excel as an output format is so they can manipulate the data using Excel functionality. &amp;nbsp;What you are asking is to restrict this, so the question arises, why use Excel as output format? &amp;nbsp;If you want to display data and make it hard to change, use PDF or something similar.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Next we have the technical limitations. &amp;nbsp;In most cases creating an Excel file from SAS doesn't happen. &amp;nbsp;It creates a markedup text file which can be "interpreted" by Excel which then renders this. &amp;nbsp;As this is a text file it cannot have the technical abilities that the Office format has (Open Office meaning a zip file containing XML snippets and possibly binary components). &amp;nbsp;As far as I am aware Excel is not even available under Unix, so how would you go about using their tech on a system they dont run on?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So I would first suggest that you assess what you are trying to achieve, what is the data to be used for. &amp;nbsp;If it is data transfer, then setup a data transfer agreement, fix the file structure and use a proper data transfer format - CSV or XML for instance. &amp;nbsp;If the data is for a report, use a proper report format, RTF, PDF etc. &amp;nbsp;If however you are trying to interact with someone else's dodgy Excel setup (which often seems to be the case - i.e. "but I have this lovelly colored excel file that I want to put data into") then consider the problem reversed. &amp;nbsp;You can easily create a CSV file from the data. &amp;nbsp;Now that CSV file can easily be opened using VBA in the Excel users end, and done with as they like. &amp;nbsp;I mean is it really your responsibiliity what someone else does with a file provided?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 09:57:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Export-protected-Excel-workbook-using-UNIX-SAS/m-p/242002#M308989</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2016-01-06T09:57:15Z</dc:date>
    </item>
  </channel>
</rss>

