<?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: String variables not accessable when read with Proc Import from Excel in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289172#M59618</link>
    <description>&lt;P&gt;The problem could be a number of things. &amp;nbsp;CAn you extract a bit of the imported dataset, into a datastep and post here:&lt;/P&gt;
&lt;P&gt;This post:&lt;BR /&gt;&lt;A href="https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712" target="_blank"&gt;https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Shows how to do it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And then show us the logic you are trying to apply to it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do note that using CSV would always be my preferred solution - fix your datastep import program based on the specifications document agreed with the vendor. &amp;nbsp;This minimises issues. &amp;nbsp;Excel is not a good data medium.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Aug 2016 12:07:47 GMT</pubDate>
    <dc:creator>RW9</dc:creator>
    <dc:date>2016-08-03T12:07:47Z</dc:date>
    <item>
      <title>String variables not accessable when read with Proc Import from Excel</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289161#M59616</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm having a problem in using PROC IMPORT to import excel files into SAS. I'm using the following code:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;PROC IMPORT DATAFILE="FILE.xlsx"
	DBMS=xlsx replace
	OUT=FILE;
RUN; &lt;/PRE&gt;
&lt;P&gt;It appears to be everything ok with the dataset. However, when I try to referece string variables (for instance, "IF VAR='STRINGVALUE') I never get anything as a result. I used trim, strip and compress to check if there was any problem with blanks and it didn't work. I imported the dataset as CSV and it worked right. Proc Contents doesn't show anything unusual with dataset attributes. Does anyone knows what the problem may be?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2016 11:51:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289161#M59616</guid>
      <dc:creator>dmanteigas</dc:creator>
      <dc:date>2016-08-03T11:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: String variables not accessable when read with Proc Import from Excel</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289171#M59617</link>
      <description>&lt;P&gt;Could you show as the offending data step code and the output of proc contents for the imported dataset WORK.FILE?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2016 12:05:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289171#M59617</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2016-08-03T12:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: String variables not accessable when read with Proc Import from Excel</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289172#M59618</link>
      <description>&lt;P&gt;The problem could be a number of things. &amp;nbsp;CAn you extract a bit of the imported dataset, into a datastep and post here:&lt;/P&gt;
&lt;P&gt;This post:&lt;BR /&gt;&lt;A href="https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712" target="_blank"&gt;https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Shows how to do it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And then show us the logic you are trying to apply to it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do note that using CSV would always be my preferred solution - fix your datastep import program based on the specifications document agreed with the vendor. &amp;nbsp;This minimises issues. &amp;nbsp;Excel is not a good data medium.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2016 12:07:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/String-variables-not-accessable-when-read-with-Proc-Import-from/m-p/289172#M59618</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2016-08-03T12:07:47Z</dc:date>
    </item>
  </channel>
</rss>

