>>Just my 2 cents worth here. I'm not a VFP expert but I had an similar problem with a table in an Access database. You might want to consider 1) creating a table in tempdb that will match the VFP table structure 2) doing one large insert into that table from VFP 3) creating the appropriate index on the temp table - this will pay off for the join to follow ; create it after the insert for the best speed 4) doing an insert into your sql server table from the temp table for temp rows "where not in" the permanent table. There are some advantages to this: you only make one trip accross the network for the the first insert; after that all the work is done on the server. Also, all garbage collection in tempdb will be done for you as soon as you break the connection..
>
>I had to print this out and digest it, but it seems to make sense. I think this is, if nothing else, a good starting point. I'm gonna start heading in this direction. Thanks.

I had to move large amounts of VFP data to SQL before. I wrote the VFP table to a flat file, BCP'd it into a SQL temp table, and ran the update/inserts from SQL. Pass-through was too slow for the amount of records (several million). HTH...