Hi Marcia,

Thanks for the input. I'll keep this in mind on my next project. Correct me on this one, Table buffering with Pesimistic Locking Mech works with multi locks and single record situations so it'd be more flexible in the long run to stick with the Table as opposed to single or row locks and TableUpdate/TableRevert eliminate another scatter and multiple replace commands ?

Checked the book after your first reply and thought you were going to take me to task over my latest misconception.

Thanks,

Don