<?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: Column Name errors in EG 4.1 in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23068#M3602</link>
    <description>You are correct.  I made the change to the name in the "Alias" field.  Will this be fixed if I also change the label as well?  I have many existing processes created in a prior version of SAS EG which will have spaces in the column name.  It was acceptable then why not now?  Will I just need to correct each of them as they arise? &lt;BR /&gt;
&lt;BR /&gt;
Your workaround is a solution.  Thank you offering assistance - I wish there was another solution.&lt;BR /&gt;
&lt;BR /&gt;
Update:  I have found another solution which is to create a computed column containing just the field where the issue occurs.

Message was edited by: SAS_Act</description>
    <pubDate>Fri, 24 Apr 2009 12:54:37 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2009-04-24T12:54:37Z</dc:date>
    <item>
      <title>Column Name errors in EG 4.1</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23066#M3600</link>
      <description>My input is a table containing codes and descriptions of codes.  My first query in the process is just to change the names of the fields.  For example, &lt;I&gt;PR_CODE&lt;/I&gt; and &lt;I&gt;PR_CODE_DESC&lt;/I&gt; are changed to &lt;I&gt;Pr Code&lt;/I&gt; and &lt;I&gt;Pr Code Desc&lt;/I&gt;.  My problem lies in the next query where EG 4.1 is saying the second field is ' "Pr Code"n Desc'n.  Is there a better workaround than changing the name?  Let me know if this is confusing beyond assistance.</description>
      <pubDate>Thu, 23 Apr 2009 21:11:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23066#M3600</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-04-23T21:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: Column Name errors in EG 4.1</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23067#M3601</link>
      <description>You have entered spaces in the "Alias" field when you renamed them.&lt;BR /&gt;
&lt;BR /&gt;
Either replace the spaces with an underscore or remove them alltogether.</description>
      <pubDate>Thu, 23 Apr 2009 22:21:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23067#M3601</guid>
      <dc:creator>DerekAdams</dc:creator>
      <dc:date>2009-04-23T22:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: Column Name errors in EG 4.1</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23068#M3602</link>
      <description>You are correct.  I made the change to the name in the "Alias" field.  Will this be fixed if I also change the label as well?  I have many existing processes created in a prior version of SAS EG which will have spaces in the column name.  It was acceptable then why not now?  Will I just need to correct each of them as they arise? &lt;BR /&gt;
&lt;BR /&gt;
Your workaround is a solution.  Thank you offering assistance - I wish there was another solution.&lt;BR /&gt;
&lt;BR /&gt;
Update:  I have found another solution which is to create a computed column containing just the field where the issue occurs.

Message was edited by: SAS_Act</description>
      <pubDate>Fri, 24 Apr 2009 12:54:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Column-Name-errors-in-EG-4-1/m-p/23068#M3602</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-04-24T12:54:37Z</dc:date>
    </item>
  </channel>
</rss>

