>>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)

Hi Leroy,

As I stated in my original reply, it's not an easy question. Each framework solves this problem differently. I can show you our code, but it's not the best one, and my colleague is currently working on modification of it anyway. If you can search here, search for the thread "Uniqueness in indexes" (something like that) (or I'll search for you, since I searched it recently anyway). In this thread Frank Camp (if I recall correctly and don't mispell his last name) showed some code, which could be useful...