Perhaps that large dataset could be configured to use HDR so that it will
simply refresh quickly no matter where the cursor is in the dataset. Either
that or you could set a MaxRows or something so that they will always reach
the end of the dataset. There is no reason an end user should need a large
dataset open persistently. Search mode is another way to really tidy things
like this up too.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Rolf Bredemeier" <rbredemeier@...>
To: <IBObjects@yahoogroups.com>
Sent: Monday, April 08, 2002 3:59 AM
Subject: Re: [IBO] transaction question


> Dear Jason,
>
> thanks for the time you spend for me. I will try
> to check the things you suggested!
>
> I think, the problem is only one application, which opens
> al large living dataset. The application is starting at morning
> by the user, opens the dataset for browsing, searching
> and editing. And the transaction is still open whole time.
>
> But, when i close the transaction, reload takes time and the
> users will be discontented...
>
> Now i will start searching the FAQ.
>
> Thanks again!