> No, this gap always present if you have connected application with
> opened select. Any statement is performed within transaction context,
> some connectivity components mask it.

This is true of component sets which do not have an architecture to use
server resources efficiently.

This isn't true of IBO. A buffered dataset can be opened and fetch records
and close the resources on the server (cursor) which require the transaction
handle to be held onto. IBO allows this to happen automatically in many
situations. It even virtualizes large datasets allowing transactions to come
and go while maintaining a partially fetch buffer of records. It just drops
and obtains cursors as needed to produce a dataset on demand.

I have written extensively on what items to remain that will "hang up" a
transaction handle on the client. If you are using IBO I recommend you bring
this issue over into our support area for fine tuning on your use of it.

I wouldn't tolerate a gap of 30,000. If you knew what overhead this imposed
upon your server you wouldn't do it any longer.

FWIW,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com