I don't recall seeing a proper answer to this question. You are correct
that AttemptMaxRows is only when automatic oat processing is happening. If
you set it to caFetchAll it will fetch all rows. The only thing you can do
to contain it is set the MaxRows of the query itself. Alternatively is to
use the HDR (horizontal dataset refinement) features and have the query
refresh (close/open) itself, which isn't totally instantaneous but
relatively quick.

Jason Wharton

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Stephen Boyd
> Sent: Wednesday, October 26, 2005 9:25 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] CommitAction
>
>
> 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?
>
>
>