<?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 Extended IntervalMatch problem in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216790#M70065</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You don't want the extended syntax here. The extended syntax is telling the system to merge the two tables based on IPNUmber (in Start/End range) and LocID. But there's no LocID on the Session table, so the merge doesn't work, and wasn't what you wanted anyway.&lt;/P&gt;&lt;P&gt;All you want to merge on is the IPNumber vs. the Start and End. That's just a regular syntax. To get the LocId back onto the Session table, you'll need a second join.&lt;/P&gt;&lt;P style="padding-left:30px;"&gt;LEFT JOIN ([Session])&lt;BR /&gt;INTERVALMATCH (IPNumber)&lt;BR /&gt;LOAD&lt;BR /&gt; Start&lt;BR /&gt;,End&lt;BR /&gt;RESIDENT [IPLocation]&lt;BR /&gt;;&lt;BR /&gt;LEFT JOIN ([Session])&lt;BR /&gt;LOAD *&lt;BR /&gt;RESIDENT [IPLocation]&lt;BR /&gt;;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Apr 2010 19:54:27 GMT</pubDate>
    <dc:creator>johnw</dc:creator>
    <dc:date>2010-04-16T19:54:27Z</dc:date>
    <item>
      <title>Extended IntervalMatch problem</title>
      <link>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216789#M70064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the problem with this example?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 19:24:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216789#M70064</guid>
      <dc:creator />
      <dc:date>2010-04-16T19:24:05Z</dc:date>
    </item>
    <item>
      <title>Extended IntervalMatch problem</title>
      <link>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216790#M70065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You don't want the extended syntax here. The extended syntax is telling the system to merge the two tables based on IPNUmber (in Start/End range) and LocID. But there's no LocID on the Session table, so the merge doesn't work, and wasn't what you wanted anyway.&lt;/P&gt;&lt;P&gt;All you want to merge on is the IPNumber vs. the Start and End. That's just a regular syntax. To get the LocId back onto the Session table, you'll need a second join.&lt;/P&gt;&lt;P style="padding-left:30px;"&gt;LEFT JOIN ([Session])&lt;BR /&gt;INTERVALMATCH (IPNumber)&lt;BR /&gt;LOAD&lt;BR /&gt; Start&lt;BR /&gt;,End&lt;BR /&gt;RESIDENT [IPLocation]&lt;BR /&gt;;&lt;BR /&gt;LEFT JOIN ([Session])&lt;BR /&gt;LOAD *&lt;BR /&gt;RESIDENT [IPLocation]&lt;BR /&gt;;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 19:54:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216790#M70065</guid>
      <dc:creator>johnw</dc:creator>
      <dc:date>2010-04-16T19:54:27Z</dc:date>
    </item>
    <item>
      <title>Extended IntervalMatch problem</title>
      <link>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216791#M70066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got it.&lt;/P&gt;&lt;P&gt;I thought, It should add LocID from range of Start/End for the IPNumber.&lt;/P&gt;&lt;P&gt;Thank you very much.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 21:09:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Extended-IntervalMatch-problem/m-p/216791#M70066</guid>
      <dc:creator />
      <dc:date>2010-04-16T21:09:51Z</dc:date>
    </item>
  </channel>
</rss>

