>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Hi Benoit,

Record count is only (a small) part of your problem, it's the data access bottleneck that's hurting you. You have to either change the access mechanism through accessing the VFP data from a VFP app using native DML -or- you have to move the data to SQL Server to take advantage of the faster access provided by a native OLE DB provider.

>And SQL Server is discussed but since the table where the updates are causing problems have about 300,000 records then VFP should not be the problem. Am I right?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

But, Benoit, I have worked with ADO in VB updating VFP tables of about that size and I have not seen such a dramatic slowdown as you report on updating... so in addition to everything that John has mentioned, I think something else, in the code, may also be going on...

Finding that issue, if I am right and one exists, may buy back enough speed to make it worthwhile to hold on until the VFP OLEDB provider becomes available... or maybe not...