Stephen Boyd wrote:

> I have been unable to find anything in the help files regarding this,
> so here goes:
>
> For TIBOQuery.CommitAction = caFetchAll is there any way to limit the
> maximum number for rows fetched when Commit is called? There is
> TimeoutProps.AttemptMaxRows but that would seem to only apply when IBO
> is attempting to automatically commit a transaction. Does this
> property also apply when explicitly commiting a transaction?

Try putting your update into it's own transaction. Then you would not
use a Query at all and only need to refresh things in the other
transaction(s) when you have finished. I tend to keep the 'heavy' stuff
isolated from the user interface with different transactions and
sometimes even different sessions.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services
Treasurer - Firebird Foundation Inc.