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.

+++ Rick ---

>>Sorry I meant CursorAdapter. It's one of the most awkward abstraction APIs I've ever seen for doing data access :-) The functionality it provides is decent but the way code has to interact with it is ugly at best IMHO. I never used it beyond playing with it for that reason.
>>
>>To me the straight forward approach of SQL Passthrough is simply more transparent and allows you full control over the entire data access process...
>
>I take cursoradapter to be an eventhook on SPT. Whatever you do with your alias (requery, update), some events in the CA will fire, and you'll have a chance to either leave them on automatic or intervene. Once it's tamed, it is very useful and can do a lot for you. It's the taming that takes some time and hair pulling.
>
>Now that I'm using one (tamed CA written by someone else who did the groundwork for me :), I'm happy with it. It's like "see ma, no hands!". And I still have the same level of control as with SPT, and in some aspects even better.