Cetin,
Thanks for your answer.

I forgot to mention that this import process occurs once per week. What basically happens is that each week about 30% percent of the payment instructions that we receive already exist in SQL Server. That's why I would like to simply pass each record and have SQL Server figure out what to do.

If I do it on the client, then I have to send the data multiple times.

>Daniel,
>Without complexities of your design what I think :
>Since you first parse in VFP what about doing unification on VFP side first. Once in a cursor/table say TableA :
>
>select * from TableA ;
>union ;
>select * from TableA ;
>into cursor crsUnique nofilter
>
>Problem how would you send this to SQL server. I would create the table on SQL server, do a remote view, append to it and update. Or an ADO connection, add to recordset and updatebatch. Without BCP operations this sounds to be really slow.
>
>Cetin