>Suppose that makes sense - if you're using TableBuffering which i also always found to be fairly redundant if you have an adequate business layer. All the buffering I tend to do is done is not done on data records but on objects that are only written into the database when they are final - no need to buffer. I've always thought of this as an odd model that makes sense only if you work on data directly which IMHO is a bad design choice in the first place.

That's what I'm using in several places - even binding controls to something like this.oengine.oRec.fieldname - and then doing a gather in oEngine.save() - which then passes the process to a handler (with CA in its belly). Most of the rest of the app works with cursors, as there's tons of code older than the invention of the CA, so that's what is used, and it works flawlessly. The handler also takes care of buffering, save-time validations, transactions etc.