This was a request from me that Jason kindly implemented ;)

Purpose is to be able to use a ReadCommited+ReadOnly transaction for
browsing (this will not block GC), and another transaction (with
different isolation and writeable) for DML (inserts/updates/deletes).
For now, I only tested it used with cachedupdates, and it worked fine
in my tests.

Unfortunately, I still didn't have enough time to test all variations
of usage.

As far as I remember, if you don't explicitly specify an
IB_Transaction, and IB_TransactioForUpdates is set, IBO will
automatically use an internal RC+RO transaction for browsing. Jason
will correct me if I'm wrong.

[]s
Carlos H. Cantu
www.FireBase.com.br - www.firebirdnews.org
www.warmboot.com.br - blog.firebase.com.br

DR> Hi,

DR> I'm noticing a new property called IB_TransForUpdates. Does it mean
DR> that I should be able to assign a read-only TIB_Transaction to the
DR> IB_Transaction property and assign a read/write TIB_Transaction to the
DR> IB_TransForUpdates? Or, do I have it wrong? Because when I try to
DR> set it up that way, I can't edit a record.

DR> --
DR> Daniel Rail
DR> Senior System Engineer
DR> ACCRA Group Inc. (www.accra.ca)
DR> ACCRA Med Software Inc. (www.accramed.ca)