Hello

Either I've been completely mistaken about TIB_Transaction::Isolation
works with a setting of tiCommitted, or there's some property I've
not set...

My app displays a list of rows within a TListView. When the user
wants to edit a row, a dialog appears and a new transaction is
started: tiCommitted, LockWait=false, RecVersion=true.

When testing with two instances of my app, I simultaneously edit the
same record and make changes in app 1 and then commit the changes.
Then when I come to commit app 2 (after making no changes) it commits
OK with no exceptions.

I had expected that when app2 committed it's changes, to receive an
exception because that row had already been updated by app1. This is
not the case, whichever of the two applications commits last, updates
the db with their copy of the data.

Is this how tiCommitted works? When App1 commits changes, are these
changes availble to App2, can the App2 TIB_Query tell me if the row
has been changed elsewhere, or do I need to refresh the row?

TIA

David

Using FBv1.5ss/W2k, BCBv5, IBOv4.2i