>
>I know this is going to sound really simplistic, but...
>
>I had a slow response problem when a PK on one of my tables was a concatenation of 2 fields. When I changed the PK to a single surrogate integer field, performance was as fast as expected. I also do not update the PK field when sending updates. For inserts, my PK is generated by a SP stored in the database.
>
>If the fields getting updated are involved in indexes, you are taking a good hit there as well. This is also, obviously, true of inserts.
>
>Is the DB VFP, SQL Server, Oracle? I am guessing VFP.

Hi Mark,

PK is OK, no problem there. There are indexes on the table (160Mb CDX). I'm looking at queuing the inserts (MTS style). The client already have a queue system in place for other tables.

VFP back-end at the moment. Oracle being invested at the moment (they've had their fingers seriously burnt by consultants who cost thousands and did nothing). They need a quick solution in VFP.