For me, buffering was handy if there were any problems with the data. For example, if I tried to write a duplicate primary key and the tables weren't buffered, foxpro would trigger a error. But if the tables are buffered, you can detect the error much more nicely with the tableupdate command and aerror().

>I have created a model for an application in which the database is updated via SQL UPDATE and INSERT statements. I manage the transactions and the effect of success/failure of the transactions by monitoring the _TALLY variable. I didn't feel any need to utilize buffering.
>
>Is there a deficiency(ies) to this approach? Are there advantages to this approach?
>
>FWIW, I am expecting to migrate the database to Oracle where VFP is simply the front end. My impression is that my model would be closer to this possible client/server model (which I would perceive as a positive aspect).
>
>Thoughts?
>
>Thanks.