Hi Hi Allan,

Shouldn't you in this case unduplicate that table first before processing?

>Hi Sergey,
>
>I came up with an alternative approach to solve the problem.
>
>However, to answer your question, one of the many functions of this application is to import largely 'unformatted' print files from two sources (after I've done all the required parsing) and then it runs a SP to find records in one table that match those in another table. To do this, I concatenate six fields in each table - and use the results to update a field named MatchCriteriaVC which, under normal circumstances, will always be unique - and do the matching based on the contents of MatchCriteriaVC in both tables.
>
>The problem arises when one of the input files erroneously has a record appear twice (in error).
>
>At any rate, I've taken a different approach to solving this problem.
>
>Al
>
>>Hi Allan,
>>
>>What field(s) in the SecondTable table define which occurence is first and which is second?
>>