Hi Nancy, (and all who had responded to my original post)

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

It's in Chapter 17 of the developer's guide. Page 452. It's not in the online docs.

To all of you, an acceptable solution to the problem was that I had SET REPROCESS set to 1, thus on any update, VFP would just try to lock the table header once, and if not successful, generate an error. With many users, this occured often.

Setting the reprocess to automatic eliminated the problem. Also, since all updates are buffered, the wait time increase for the user waiting to get a table header lock to update the table is a non-issue.

Phil