Bruce,

Table buffering doesn't require multiuser or client server. Single user works just as good using buffering. You drag/drop fields out of the DE or from the project manager. The private datasession feature also allows you to easily let your users open the account form more than once to see multiple clients.

Scatter/Gather would work, just not near as well as binding to tables IMHO. Memvars have scoping issues that make things more complicated. VFP is fundamentally different than FP2.x. You have the option to just keep on doing things the 2.x way or spend a little time to learn OO and use the new features VFP gives you to make your life easier in the long run.

If you are using some other SQL backend Views can make the backend look just like a normal VFP table to your app. And the buffering still allows easy update/revert functionality.

>After trying to digest what you attached I realized that these new conventions of buffering are to make multiuser and client server applications more robust and dependable.
>
>My application I am writing is basically a single user application so I SET EXCLUSIVE ON to make my life easier and everybody is happy with this. So the table buffering is irrelevant for what I do. Since my input screens are real simple perhaps GATHERing and SCATTERing to memory variables referenced on forms would work just fine.
>
>After reading this arcane buffering stuff the question comes up in my mind is if you're writing to MS SQL or Oracle SQL, doesn't the SQL engine take care of all this?