Solved! Go to Solution.
It still behaves the same, in different scenarios. In the case i'm dealing with it's EAST LAKE or WEST LAKE. I had been using the locator to help find data gaps, however, i just discovered that an address coming in a E LAKE matches because it views the E as EAST. Normally fine, but for my workflow not fine. What was your work around?