>Cristian;
>
>Rob and Jim bring up good points.
>
>I have a few comments or questions which include what Rob and Jim stated.
>
>1. Private Data Sessions

Yes

>2. Remove RECCOUNT()

this was taken from a prvious thread (i don't remember wich) with discussion on same behaviour

>3. Remove Delete

this was taken from Tastrade example but I supose is useles because I have primary key value just from beggining of append record through default value

>4. Use of INSERT and APPEND?

APPEND for creating a new blank record on buffered table wich are then editted, suppose can change the insert to append; or you want meen else

>5. Are Primary Keys used?

Yes

>6. How are the values of ldatamaste.and ldataslave created?

at design time and never changed in run time and contains alias for parent and child

>
>If you are using VFP 6, check chapters 17 and 22 of the Help file. Also, consider using an error trapping routine within your Save code. This should include SET Reprocess, and Retry routines.
>

I have a error routine in error event of form wich treat most of errors related to buffering (update conflict, unique keys, field and table rule ...); if you want I post error routine but is long

What with SET REPROCESS ? in error routine or in save

I am using VFP6, I plan to upgrade to VFP7 since we have SP1


>Concerning your primary or unique key, I think how this is generated and propagated is the basic problem. I wish I could see all factors involved with this problem. I think the use of a Transaction is important with this type of procedure and I am glad to see you are using it.

The primary key are stored in idkey table with fields tablename/chrpart/nrpart from where are taken like :
rlock
increment
update
unlock
return value

and stored in table through defaultvalue of field in DBC; I don't have two records with same key but from 2 recs appended (one from every PC) I get only one in parent (it seems not hapen in child)

>
>I think we are getting a good focus on the problem, and a bit more information will help us to assist you. :)
>
>Tom