>>Um, I wasn't clear and have omitted part of the context. .CursorRefresh() is grid safe if you're OK with the same SQL command being used over and over. If your grid needs to contain search results, with custom where clause every time, then setting .selectCmd to this new command and .cursorFill() are needed, but then it's not grid safe any more.
>
>Sigh - no need to worry about early Alzheimer here today ;-)
>As I surmised the OP was only after records changed/added/deleted by other machines/program instances, that case would be covered.
>
>Even for the UC of different WhereFilters in SelectCmd needed, I probably would try if a special CA could handle the safe select gymnastics with a few lines of code to keep data layer on one mechanism ;-))

I'm still investigating... the source of my problems may be the weird behavior in cases when there are two adapters on the same base table, and one of them gets requeried (by either .cursorRefresh(), requery() or refresh()) - first time it may work, second time it seems the cursor of the other one gets closed. Or something like that, still haven't gathered all the evidence.