Subject Re: RE: [firebird-support] Keep that OAT moving

Thank you for the reply. Sorry I did not see this till today
I am writing down what I have understood from you comment. Is this what you meant.

Currently we are refreshing the transactions like this

I have 2 Tdatasets opened with one TIBOTransaction object <tran> and
On a timer event i have the following statement.

You are saying as a first step that this should change to
Re-Open all the Tdatasets opened with this transaction
Suppose my timer is firing once every 5 minutes, does this mean OAT is stuck for 5 minutes

Alternatively will this be better

Thanks for you help


------------------Original Message-----------

From : "Richard Pendered" <rpendered@...>
To : <>
Date : 01/08/2003 1:27:28 PM
Subject : RE: [firebird-support] Keep that OAT moving

A simple way would be to have a transaction for each open TDataset, then
when refreshing Commit and restart the transaction affected by the refresh.

-----Original Message-----
From: GOVINDKRISHNA [mailto:gkrishna@...]
Sent: 01 August 2003 08:28
Subject: [firebird-support] Keep that OAT moving

Hi List,

After seeing some of the recent posts in the list. I realise "I dont know

The burning issue right now is the correct way to retrieve data and make
that the OAT doesnt get stuck.

I will describe my app (It is a mail cum discussion forum app). It is an MDI
app. There is mail window. There is a discussion forum window.

I need a TDataset (I am using a TDataset compatible grid for various
for each of these screens. This is a display only dataset. User may request
refresh or there may be a timer based or event based refresh of this screen.

There is a another screen which allows the user to open an particular record
see all the details. I would like to bind this to the same dataset so that
user can scroll with next and previous seeing all the details.

There is another screen which basically has to insert data into the
database. (
TDataSet components again)

Would be grateful if somebody would give me some kind of skeleton for
retrieving and updating data appropriately for this. The emphasis is on what
needs to be done to make sure that OAT is not getting stuck and it is the
fastest way to do thing.



To unsubscribe from this group, send an email to:

Your use of Yahoo! Groups is subject to

To unsubscribe from this group, send an email to:

Your use of Yahoo! Groups is subject to