Normally I would, and actually I have. My problem is that I am replicating two MSSQL2K tables, with a total of 4.6 million rows, to two VFP tables. The problem is that using SQL-Insert results in 4.6 million VFP "transactions", which takes about 2 hours on a dual-processor 1.2GHz system with 2gb of RAM. The tables total 270mb, but I am not writing a 270mb file, I am repeatedly writing a 1.1k stream 4.6 million times, inside of the VFP OLEDB driver.

I was thinking that a good alternative would be to write everything from MSSQL to a tab-delimited text file and then append that file to my table. That way, I would be doing a 270mb copy, then a 270mb copy.

My frustration level is *high* on this one. The docs say I can do it, but I can't do it. Can anyone recommend a way to go about this short of opening a per-pay incident with Microsoft?





>I would work with VFP OLE DB provider the same way as with SQL Server, use set oriented SQL commands (Insert, Update, Delete) or create Recordset and use it to update VFP table.