<?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 Generated Code for Excel Import in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Generated-Code-for-Excel-Import/m-p/140603#M11269</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;(1) I tried to import an xls file on EG using the SAS/ACCESS to PC files method and when I check the generated code the path of the datafile is pointing on where the xls file resides, which is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(2) On another machine, I tried the same approach but when i check on the generated code I can see that the path on the datafile points to an xls file pointing to the work directory and seems to be a copy of the original xls file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas how to always get (1) when the excel generates the code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 May 2014 15:12:48 GMT</pubDate>
    <dc:creator>milts</dc:creator>
    <dc:date>2014-05-01T15:12:48Z</dc:date>
    <item>
      <title>Generated Code for Excel Import</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Generated-Code-for-Excel-Import/m-p/140603#M11269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;(1) I tried to import an xls file on EG using the SAS/ACCESS to PC files method and when I check the generated code the path of the datafile is pointing on where the xls file resides, which is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(2) On another machine, I tried the same approach but when i check on the generated code I can see that the path on the datafile points to an xls file pointing to the work directory and seems to be a copy of the original xls file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas how to always get (1) when the excel generates the code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 May 2014 15:12:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Generated-Code-for-Excel-Import/m-p/140603#M11269</guid>
      <dc:creator>milts</dc:creator>
      <dc:date>2014-05-01T15:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: Generated Code for Excel Import</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Generated-Code-for-Excel-Import/m-p/140604#M11270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If your SAS session is on a different machine than your local PC (or where your Excel file resides), then EG needs to move a copy of the file to SAS for importing.&amp;nbsp; That might be what you're seeing in the generated code with the WORK directory reference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could use the &lt;A href="http://blogs.sas.com/content/sasdummy/2012/12/06/copy-files-in-sas-eg/"&gt;Copy Files task&lt;/A&gt; to move the Excel file first, and then perform the Import Task using the file in the server-based file system.&amp;nbsp; But that still leaves the "copy step" unaccounted for within your SAS program -- in case you are looking to reuse that program elsewhere.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 May 2014 16:31:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Generated-Code-for-Excel-Import/m-p/140604#M11270</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2014-05-01T16:31:56Z</dc:date>
    </item>
  </channel>
</rss>

