<?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: 'proc import' versus libname for importing a xlsx file via pcfile server. in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162963#M300082</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've never struck the problems you are having with PROC IMPORT hence the choice of using IMPORT versus LIBNAME comes down to what it is to be used for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PROC IMPORT is ideal for importing a single worksheet where you wish to explicitly name the output SAS dataset. The LIBNAME approach I find is better if you are importing several sheets from a workbook and want SAS to take care of the output dataset names. I find using PROC DATASETS with the LIBNAME is great for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We don't use the PC File Server as we use the 64-bit MS Office components with 64-bit SAS to avoid "bitness" issues that the PC File Server addresses, and it works very reliably.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 28 Sep 2014 18:51:34 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2014-09-28T18:51:34Z</dc:date>
    <item>
      <title>'proc import' versus libname for importing a xlsx file via pcfile server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162962#M300081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What are the pros and cons of each method? Which is better?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Historically I have tended to use a proc import statement to import data from a xlsx file, but lately I have noticed the process will hang. The only work around which appears to work is by creating a pcfile libname and accessing the data that way....which leads me to wonder what are the pros and cons of each method. Is the libname the 'better way?'xls&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 28 Sep 2014 15:13:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162962#M300081</guid>
      <dc:creator>kruzewski</dc:creator>
      <dc:date>2014-09-28T15:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: 'proc import' versus libname for importing a xlsx file via pcfile server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162963#M300082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've never struck the problems you are having with PROC IMPORT hence the choice of using IMPORT versus LIBNAME comes down to what it is to be used for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PROC IMPORT is ideal for importing a single worksheet where you wish to explicitly name the output SAS dataset. The LIBNAME approach I find is better if you are importing several sheets from a workbook and want SAS to take care of the output dataset names. I find using PROC DATASETS with the LIBNAME is great for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We don't use the PC File Server as we use the 64-bit MS Office components with 64-bit SAS to avoid "bitness" issues that the PC File Server addresses, and it works very reliably.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 28 Sep 2014 18:51:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162963#M300082</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2014-09-28T18:51:34Z</dc:date>
    </item>
    <item>
      <title>Re: 'proc import' versus libname for importing a xlsx file via pcfile server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162964#M300083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only time I've run into issues is when you're dealing with SAS 64bit and Office 32 bit. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I prefer the libname method in general myself because you can see the file before 'importing', but that has nothing to do with functionality. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 28 Sep 2014 22:13:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/proc-import-versus-libname-for-importing-a-xlsx-file-via-pcfile/m-p/162964#M300083</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2014-09-28T22:13:51Z</dc:date>
    </item>
  </channel>
</rss>

