> OK, I see now. In that case, how about the AfterFetchRow in the

detail

> dataset, or is your processing something you have to do at the end

of the

> query when all rows have been fetched ? If so, then would the

AfterExecute

> event help (or AfterFetchEof if it is an TIB_CURSOR and not an

TIB_QUERY)

> I've never used them myself, yet, so I'm not 100% sure.
>

My processing would be something "consuming" all rows of the detail
dataset. Even if they have not been completely fetched, my processing
would do that by iterating through all rows of the detail.

AfterFetchRow in the detail wouldn't work, as it is called for each
row. AfterFetchEof would not work either, as there is no one fetching
all rows upon requery

AfterExecute might work ... i'll give it a try. Luc pointed to
AfterOpen with some mode set to raOpen. Might work as well

Mirco