Mike..

I mean that updates are either incomplete or some sort of OLE-DB error kicks in that is difficult to trap. If on the other hand, I use stored procedures, I take control of the entire process. This is why the Command Object is the most powerful element of ADO. The recordset is fine for data presentation. It's buffering capabilities are OK as well. After that, it become rather mediocre.

And yes, at times, the recordset becomes impractical. For example, I might be forbidden to render client-side updates/inserts/deletes.


>By "break down", are you seeing data corruption/loss problems, or does it just become unwieldy and impractical?