With all due respect to my esteemed East Coast collegue <g>, I like optimistic table buffering for child tables and optimistic row buffering for parent tables...

>>Can someone give me an idea on what is the best way to use buffering in a network environment.
>>Row vs. Table, or good old reclock()
>
>In my not-so-humble opinion, setting Optimistic Table Buffering in each Cursor
>in the DataEnvironment is the way to go. Then, you can write code in your form's
>Save method that checks the CURVAL() and OLDVAL() to see if anyone else has
>made changes while you've been working....