>>We're using GUID for PK, so they had to be calculated on each insert using SP. That's time spent, of course, but there is nothing I can do about it.
>
>You're using GUID for PK? Excellent.
>"on each insert using SP. That's time spent, of course, but there is nothing I can do about it."
>Wrong! Of course you can and save considerable time. With an SP it's likely code has API declaration in it. If you move API declaration outside SP and use your own code instead you might save minutes. API declaration is time consuming.
>

Hmmm, I'll play with this idea. Sounds like another good one.

>"(using temp cursors), but will lead to a complex code re-write" I'm not sure the code would be more complex. To me it looks like it'd be less complex.
>PS: No RI code is the most clever RI code.
>Cetin

In my tests I disable RI using special variable (my RI code has ability to turn it off), but I don't see how RI come to play until saving time. All data are in buffered 5 mode, RI is not happening until tableupdate(.t.)