> I have an application with browsable dbgrids. Whenever a grid is open
> the OAT stops moving.
> I have tried many variations of "TimeoutProps" settings on the
> Transaction to no avail.
> The only solution I found was to create a timer to auto commit every 5
> seconds. and have all my TIBOQuery's commit action on invalidateCursor.
> This works fine, except for the fact that the datasets get very slow
> (browsing, incremental search, etc...)
>
> I had an idea to have the datasets use a readonly/read commited
> transaction, and do all my updates,inserts and deletes with another
> query connected to a read/write transaction.
> but the problem with that is that the dataset insists on being read-only
> when connected to a read-only transaction.
>
> Is there a better way of doing this?

That is not the direction I would go.

I suggest you learn the ropes on search mode and you have your users let the
server do the searching instead of their eyes. This way they type in a
little criteria and only the records of interest appear.

The other possibility is to cause your datasets to fetch all the records
from the server.

How many records are being fetched into the buffer? If its more than a page
or two then I would have to say your users are being shown too much data.

Perhaps you can tell us more about your application.

Remember, the rule of thumb with client/server is to let the server do as
much work as can be pushed to it because that is where your muscle is,
unlike in PDOX where all the muscle was actually in the client.

HTH,
Jason Wharton