>Hi Agnes,
>
>-------------
>It's not that bug that frustrated me. I never run into it - I stopped befor. The problem is that I need to get next free PX, lock the next n records, APPEND / or INSERT. This will be not that tricky if I'm exclusive but I'm shared. The real problem is to get the next PX easy (AFIELDS is a kludge) and to set it n-steps forward, so that I 'own' those PX's. I know I can set next AutoInc with ALTER TABLE, but for the first im non exclusive, and for the second this will result in a DBC bloat. And I will insert some records not alter the table.
>------------
>
>This is not a VFP problem, this is a intrinsic InsertLock operation, on any implementation possible, you need to put a RLOCK(0) before the operation.
>
>Fabio

I know - but I don't like, with the old PK table it was no problem so why should I change?

Agnes