>I read something today in Foxpro Advisor that said that optimistic buffering (either row or table, I don't remember which) is the most useful, effective, popular, something like that when working with client/server stuff? Why would this be so? Isn't that the one where two people can work on something but the last one to save it "wins" and the first one loses all their changes? Why would I want to set up such a situation as opposed to using pessimistic and not even letting that second person get in (of course, most of the time it would be row buffering since table pess defeats the multi-user stuff)?
>
>I'm figuring I must have missed something. Thanks in advance for cluing me in.
>
>Denise
Denise

Optimistic buffering doesn't have to be mean that the last one wins
if/when you see a conflict you can do all sorts of stuff including letting the user decide or letting the first one win etc.
also note that you can set it so that the last one wins happens on the field level - i.e. if 2 users update different fields both their changes register

Arnon