At 09:21 AM 29-07-02 -0300, you wrote:

>Svein,
>
>Thanks for your help. It was very appreciated... Your solution is very
>interesting...
>But i think there is a more "ibo oriented" solution, so somebody could say
>something about it ? Helen ? Geoff ? Jason ?

I'm a real chicken about questions like this. I thankfully departed from
CachedUpdates when I started using IBO.

As far as I know, the way you are doing it is the way to do it. Cached
updates isn't very "ibo oriented" anyway; since IBO is oriented towards
taking advantage of the concurrency support offered by the IB/FB
transaction model. As soon as you separate the data from the database with
cached updates, clientdatasets, memory tables or whatever, you lose that
"cover" and simply take your chances about whether the data would be
changed during the time the dataset was "off-line".

The "ibo oriented way" would be to stay under transaction control and use
the TimeOutProps to shout at the user (warn or prompt) when a transaction
has gone too long and to shut the transaction down eventually.


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at
www.ibobjects.com