With all due respect, Michelle (and to any *lurkers*), buffering and transactions are important to understand. I've been reading (and cringing) through this thread at the thought of just sticking in table buffering and tableupdates everywhere because it *seems* to do the job. The problem overcome may indeed really need a different resolution.

Even in a single-user application, given the nature of Windows, you can run into trouble using an inappropriate buffering technique.

There is no "right/wrong" or "better/worse" to row vs. table buffering. Every technique has its place. That's not to say that there isn't room for disagreement in how to use which technique, but, one should at least have a sound rationale for using one over the other. And you can't really have that unless you understand all of them.

There are any number of primers on these topics, including MS KB white papers on the subject. My personal favorite is Effective Techniques for Application Development with VFP 6.0 by Jim Booth and Steve Sawyer. It's very practical. Very clear.

>I suppose if I'm always doing TABLEUPDATE anyway, I guess I might as well stick with table buffering since I won't gain anything with row buffering.