>>Right now that brings up an error [maybe a bug] in the CursorAdapter. Once the TABLEUPDATE is completed, the DESTROY of the CA object fires. FWIW, this is the 4th argument, and it could be what I want if I could test it.
>
>Are you sure you passed 2 as the first argument?

To elaborate further, the bug is when the 4th parm is passed as an object property [THIS.aUpdateError] instead of a memvar. This happens regardless of what the first argument is. When I do test it with an array memvar, all I get returned is -1. This is returned when I create the CA, retrieve the data, then make a change to the same records using SQL Server Enterprise Manager, then try to save my changes in the CA. I get -1 regardless of the number of records that do not get updated. I also get no other info.