Hi Thomas!

I once had a problem where my TIB_Cursor (don't think I used a TIB_Query)
seemed to 'restart' after having fetched a lot of records and things came
to a crawl (it would start off fetching e.g. 80000 records and then the
client would wait until those 80000 records were fetched again before
proceeding and after possibly another 10 or 20 thousand rows (continuously
decreasing for each iteration) restart again...). I don't quite remember
how things got solved, but I think I tried to disable CallbackInc by
setting it to -1 or increasing CallbackInitInc beyond the number of rows I
wanted to return (I thought about setting AutoFetchAll to true, but doubt I
did that).

HTH,
Set

At 00:22 08.11.2002 +0100, you wrote:

>Using EXISTS instead of IN makes the query pretty fast. Fetching now all rows
>to the client application (to export them into different formats), the CPU
>utilizitation for both, the client application and the ibserver.exe process
>is about 45% for each. But after approx. 115.000 fetched rows, the CPU
>utilizitation for the client application falls to 0% and for the ibserver.exe
>to 99%. The only way to bring down the ibserver.exe process is to kill
>the client application.