>>Why do you want to lock record before editing? Imagine, that user hits Edit button and goes to lunch. Other user would be unable to change this record. I believe, the >common practice is to let users edit the same record, but in TableUpdate check for collisions. Last user will save and overwrite, changes by another user would be lost...
>
>That is Exactly what I wanted to do at first, but I can't Get it to work right.
>If I did O.R. buffering, would that help? and Even If I did that, How could I tell who is doing what in order to give the right response (save/overwrite)

Leroy;

First extablish your business rule. Will you allow two users to edit the same record at the same time? You can check to see if this has occured and either:
1. Save the last occurance with no notification to either user.
2. Create a rule to notify the last user that someone modified the same record just before your changes - Over Write Yes/No?

Tom