<?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: LINE and COLUMN cannot be determined.error in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347561#M80299</link>
    <description>&lt;P&gt;Yes, an easy fix. &amp;nbsp;Assuming you want matches on ID:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if info_id &lt;FONT color="#00FF00"&gt;and&lt;/FONT&gt; inmerge;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Apr 2017 01:37:04 GMT</pubDate>
    <dc:creator>Astounding</dc:creator>
    <dc:date>2017-04-06T01:37:04Z</dc:date>
    <item>
      <title>LINE and COLUMN cannot be determined.error</title>
      <link>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347560#M80298</link>
      <description>&lt;P&gt;I've been looking through the forums and have seen this issue crop up before. &amp;nbsp;It looks like it should be some form of semicolon placement but I've tried running this seperately and couldn't find the issue. &amp;nbsp;Does anyone have an idea?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to create a macro to isolate patients from one dataset (labelled "SOURCE.fo_id", for the ID variable) with any new dataset ("&amp;amp;data") - the code for this is below.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;%MACRO subset (data=);
DATA &amp;amp;data._fo;
	MERGE 	SOURCE.fo_id (in= info_id)
			&amp;amp;data (in= inmerge);
	BY ID;
	IF info_id inmerge;
RUN;	

%MEND subset;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, everytime I try to run this I'm recieving the following error message:&amp;nbsp;&lt;/P&gt;&lt;P&gt;22: LINE and COLUMN cannot be determined.&lt;BR /&gt;NOTE 242-205: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and&lt;BR /&gt;COLUMN where the error has occurred.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered this issue before or have any suggestions? Am I missing something silly?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 01:21:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347560#M80298</guid>
      <dc:creator>cyoung</dc:creator>
      <dc:date>2017-04-06T01:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: LINE and COLUMN cannot be determined.error</title>
      <link>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347561#M80299</link>
      <description>&lt;P&gt;Yes, an easy fix. &amp;nbsp;Assuming you want matches on ID:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;if info_id &lt;FONT color="#00FF00"&gt;and&lt;/FONT&gt; inmerge;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 01:37:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347561#M80299</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2017-04-06T01:37:04Z</dc:date>
    </item>
    <item>
      <title>Re: LINE and COLUMN cannot be determined.error</title>
      <link>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347563#M80301</link>
      <description>&lt;P&gt;That change worked! Thank you so much!!&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2017 01:46:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/LINE-and-COLUMN-cannot-be-determined-error/m-p/347563#M80301</guid>
      <dc:creator>cyoung</dc:creator>
      <dc:date>2017-04-06T01:46:50Z</dc:date>
    </item>
  </channel>
</rss>

