>Nadya,
>
>You might consider keeping a checksum of the incoming addresses that you propose to correct on your live database. Then the next time it comes in, if the checksum in the live database matches the checksum on the incoming data, you know you've already dealt with this address historically.
>
>Scott

Hi Scott,

That's an interesting idea. Basically, we keep previous year information (not in checksum format but rather the PStreet field in another table called AssrMstr). So, firstly I check PStreet from this year with the PStreet from the prev. year. However, we found cases, there we have the same PStreet in this year and prev. year, but the data in our live database are completely different. E.g. PStreet is 56 Main St. and Street = Abington St. What was the cause of such problem - it's a mystery, which Sherlock Holmes (I didn't get spelling right, I guess) would probably solve. But we just want to catch these cases and process them. That's why I added some logic to check, if we have information in Street and StNum in accordance with unparsed street. Now, we're using lots of different rules doing standardization, so, for example, First St would become 1st St. (That's why I exclude cases, there first letter in a street name is a digit). So, it would be a rough check and some perfect cases we would have to re-process again and again. However, Lily and Lilly case could be excluded and that's what I'm trying to achive with the revised code (see my post to Jaime).

>>Hi everybody,
>>
>>I'm trying to find a solution for the following problem: Each year (or within other reasonable period) we receive data from Assessor. We then have to process these data and put into main database. One of the processes, we're doing, is street standardization. We usually receive unparsed address from Assessor and a special application then called and performs parsing and standardizing of addresses. (My application, BTW). So far, so good. Now, obviously property address is unlikely to change, so if we done some work with addresses in the previous year, there is no need to repeat this work next year unless it's a new property or something was wrong in the database...
>
><snip>