<?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: Selection Criteria for a composite locator not working in 10 in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298922#M17129</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Original User: bwragg&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Did you ever find a solution? I am currently having the same problem.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No I didn't find a solution. I did find that the new address locators are a lot, lot quicker so I just removed all my selection queries and it just searches multiple locators. Usually get a response in a few seconds.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 Oct 2012 04:22:42 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2012-10-31T04:22:42Z</dc:date>
    <item>
      <title>Selection Criteria for a composite locator not working in 10</title>
      <link>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298920#M17127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Original User: bwragg&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In 9.3 I created 8 address locators for each of the 8 states I was working with. I used the US Single Address style. Then I built a Composite Address locator, added each of the 8 Locators and had a selection criteria like this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;"SuburbAndState" LIKE '% NSW' or "SuburbAndState" = 'NSW'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(NSW is the state and was different for each loactor)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;for each of the states locators.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So if an address was entered with the State the Composite address locator would go thru each address locator until it found the correct one, then just search that one only. e.g if I entered "5 tucker st vic" it would just go thru the list of locators and use the VIC one.It was a massive speed improvement...went from being totally unusable when we had each state in 1 massive address locator to being a really fast way to search.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have 10sp5 and would like to rebuild our address locator in 10 to get the new features and also to add another smaller set of addresses for a nearby country. So I've rebuilt the 8 address locators in 10 &amp;amp; created a 9th one for the new country. I tested them all individually in ArcMap using the Find window and they work great.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But when I create a composite address locator in 10 and enter a selection criteria similar to the above (fieldnames are a bit different but same data):&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;"State" LIKE '% NSW' or "State" = 'NSW'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;also tried just "State"='NSW'&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I get no results. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The composite address locator itself seems to be working because if I remove the selection criteria string from each locator it searches them all and I get results. E.g if I search for "5 tucker st" I get results from multiple states. But the moment I create a selection criteria string it stops working. I've using the query builder to make sure I didn't have any bad SQL and it verifies ok.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Attached is a screen grab of the composite address locators settings I'm testing with 1 of the states and the 1 other country.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[ATTACH=CONFIG]16850[/ATTACH]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;bwragg&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Aug 2012 20:49:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298920#M17127</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2012-08-10T20:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: Selection Criteria for a composite locator not working in 10</title>
      <link>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298921#M17128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Original User: doitjd1&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Did you ever find a solution? I am currently having the same problem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2012 11:47:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298921#M17128</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2012-10-25T11:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: Selection Criteria for a composite locator not working in 10</title>
      <link>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298922#M17129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Original User: bwragg&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Did you ever find a solution? I am currently having the same problem.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;No I didn't find a solution. I did find that the new address locators are a lot, lot quicker so I just removed all my selection queries and it just searches multiple locators. Usually get a response in a few seconds.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Oct 2012 04:22:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/selection-criteria-for-a-composite-locator-not/m-p/298922#M17129</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2012-10-31T04:22:42Z</dc:date>
    </item>
  </channel>
</rss>

