>>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
>
>Hi Fabio,
>
>Do I understand correctly, that in VFP8 there is no way to be able to insert records into parent table and into the child table without tableupdate on the parent?
>
>I'm using VFP8 at the moment and CA. I use AutoInc fields as my PKs.
>
>Thanks a lot in advance.

Hi Naomi,

I don't understand, if you have to insert the record in the parent table you have to make tableupdate.

Besides, if you consider that in every instant the operation can stop in anomalous way
(hw fault, os fault... ) and that there can contemporarily be another session that
ago the same thing, the ties become very restrictive.
Clearly it is possible to draw the tables so that is possible to create zombi rows
to make to revive, or to use universal keys...., but the by teacher is that to stop
the distribution of new keys during the transaction