Actually not if an unlock all is issued when the first record lock failure occurs... I guess I left that out! :o)

>Gee, Tracy, I hope not. You could potentially lock your parent record and fail on the child record and leave your parent locked!
>
>
>>IF FPD26 I used to do the following:
>>
>>

>>PRIVATE llokay
>>STORE .T. TO llokay
>>SELECT parentable
>>IF RLOCK()
>>   SELECT childtable
>>   SCAN FOR childtable.pkey = parentable.pkey
>>      IF !RLOCK()
>>         STORE .F. TO llokay
>>         EXIT
>>      ENDIF
>>   ENDSCAN
>>ELSE
>>   STORE .F. TO llokay
>>ENDIF
>>IF !llokay
>>   *Display message to user and try again or abandon
>>ELSE
>>   SELECT parentable
>>   *Start replacements stepping through all locked records
>>   UNLOCK ALL
>>ENDIF
>>

>>
>>>Sergey,
>>>
>>>I think I may have an even more complicated problem. I have several tables that hold data about a certain record. When a user makes a change the app goes through each table to make the updates. The trouble is three or four tables get updated but one table will return the 'Record is Locked' message. By this time there is not a practical way to go back and do the update. It seems that all the tables would have to be checked first before the update process begain. Any advise on this?