<?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: NODUPKEY and by _ALL_ with adjacent confusion? in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730313#M227392</link>
    <description>&lt;P&gt;"Adjacent" here means "adjacent after the sort".&lt;/P&gt;</description>
    <pubDate>Wed, 31 Mar 2021 06:46:34 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2021-03-31T06:46:34Z</dc:date>
    <item>
      <title>NODUPKEY and by _ALL_ with adjacent confusion?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730310#M227390</link>
      <description>&lt;P&gt;Hi all SAS Users,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am learning some courses provided by SAS, today when I reviewed the material, I saw this sentence.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ResoluteCarbon_0-1617172322930.png" style="width: 999px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/56731i6FE7683F622AF963/image-size/large?v=v2&amp;amp;px=999" role="button" title="ResoluteCarbon_0-1617172322930.png" alt="ResoluteCarbon_0-1617172322930.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am from a country that English is a second language, so from what I know,&lt;STRONG&gt; adjacent&lt;/STRONG&gt; means that two rows continuously in this case. So, if these two rows are not continuously, how come we exclude the totally duplicated rows?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 06:34:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730310#M227390</guid>
      <dc:creator>ResoluteCarbon</dc:creator>
      <dc:date>2021-03-31T06:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: NODUPKEY and by _ALL_ with adjacent confusion?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730313#M227392</link>
      <description>&lt;P&gt;"Adjacent" here means "adjacent after the sort".&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 06:46:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730313#M227392</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2021-03-31T06:46:34Z</dc:date>
    </item>
    <item>
      <title>Re: NODUPKEY and by _ALL_ with adjacent confusion?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730323#M227399</link>
      <description>&lt;P&gt;The explanation would have been clearer (and obviously less confusing, since it confused you) if the word &lt;EM&gt;adjacent&lt;/EM&gt; had been omitted. This word brings no value here.&lt;/P&gt;
&lt;P&gt;It's probably a leftover from an explanation about the NODUPREC option, and should be removed here.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 08:00:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/NODUPKEY-and-by-ALL-with-adjacent-confusion/m-p/730323#M227399</guid>
      <dc:creator>ChrisNZ</dc:creator>
      <dc:date>2021-03-31T08:00:37Z</dc:date>
    </item>
  </channel>
</rss>

