Hello, fdt4y!

Tuesday, July 10, 2012, 7:17:56 PM, you wrote:

f> After some more investigation I found that our main user interface
f> client app starts a single long running read transaction used to pull data for
f> display in its grids. All updates are executed in small/short
f> 'write' transactions. It is common for our client app to run 23 hours in a day (in a
f> warehouse running shifts). We use FIBPlus components which works
f> great, but now I'm faced with a catch-22. How can I commit/rollback the 'long read'
f> transaction without disconnecting the FIBDatasets which feed the
f> grids. If I do commit the read transaction, all the grids lose their content.

read-only transaction must be real read-only, not "logically read-only". So, you
need to set this transaction parameters to

read
read_committed
rec_version
nowait

--
Dmitry Kuzmenko, www.ib-aid.com