>Bruce I don't believe buffering is a safe way to do it, I will have roughly 400 users on a WAN and buffering is not "real time" so I think that one tableupdate will conflict with a second tableupdate
>
>
>I do agree if I place the tableupdate's strategically then I could make it work

It depends what you're doing...if you're just appending records, that's usually easy enough, since you only need to check for inserting a new key right at tableupdate time. Otherwise, the users can take their time editing.

If you're talking about many users possibly editing a single already existing record at once, then you'll want to lock it, perhaps.