Phil,

1. Would you be so kind as to suggest a search string so I can find your reference in the help?

2. Are you using SET LOCK?

3. Thanks for the info that you are using pessimistic row locking. It is my understanding that pessimistic locking can result in far more collisions than optimistic. Which is (one reason) why I don't use it ;-).


>Hi Nancy,
>
>>INSERT INTO doesn't lock anything at all, AFAIK...That's what TABLEUPDATE is for. What style of buffering do you use?
>
>The VFP documentation states a list of commands that "automatically" handle locking while updating, and INSERT INTO is one of them. Perhjaps I have misread the docs, but I have never tried to lock anything on an INSERT INTO in a multi-user environment before and have never had this problem.
>
>In terms of buffering, I am using pessamistic row buffing. As stated in the original post, I use an INSERT INTO to create the record (with buffering on), then issue an TABLEUPDATE() to write through to the database.
>
>Phil