🚀 go-pugleaf

I am really upset by this, and I really don't know how can I manage this
Horrible, Awful ADO error.

I'll try to explain more clearly what  need.

I am using BatchUpdates in an ADO environment with CBuilder 5 Ent. This
means that I have client cursors and that actually changes are cached until
a global command is issued to "update all changes". This allows changes on
multiple tables to be issued in a consistent way without locking the tables
for a long time.

When some DB error occurs (I am using MS Sql Server 7, but any transactional
database is ok), an exception is thrown so the Commit is not issued, but a
Rollback is, and then the error is displayed.
So, let's say we have inserted 3 rows in a grid, and that one of those three
raise an error from the database (i.e.: duplicate primary key). Obviously,
because of the transaction management, none of the three rows is saved into
the Database. I would exprct that when I correct the problem on the only
wrong row, all three rows get saved on the database, to reflect the grid
status.
This does not happen, insted only the newly modified row gets saved.

Seems that the status of the records in the TADODataSet is lost even if the
records are not saved.

I'm asking if there is a way to save that status, or if I did something
wrong, or what.

Thanks A LOT to who'll reply with sense.