>>Hmmm, it seems like a LOT OF WORK,

>< rof, l > and < lol >. It is hardly a lot of work. Only about 8 lines of code:

*** Rebuild the cursor used as the recordSource for the grid
SELECT ( This.RecordSource )
ZAP
SELECT < some field > FROM < Some Table > WHERE < Some Condition > ;
  INTO CURSOR Temp NOFILTER
SELECT ( This.RecordSOurce )
APPEND FROM DBF( 'Temp' )
USE IN Temp
GO TOP IN ( This.RecordSource )
This.Refresh()

Yeap, I know is just 8 lines of code, but if I code 8 lines in every grid I use is a lot of work for me <g>, I'm under the "Less-effort law" < ROFL >

>>I don't want to recreate the Grid after an Zapping or Packing,

>I never suggested PACKing which closes the grid's RecordSorce and blows it away. ZAPing, however, does not close the RecordSource so there is no issue of having to re-create the grid < s >.

Yeap, I know it, the post looks like I wanted to "Kill a mosquito with a lasser gun" . I just want the Grids auto-knows his binded cursor. If I can't know I just can't that's all ( I wanna cry :'( )

>generally I use Views or RecordSourceType=4.

>A parameterized view would be a good way to go. But I was under the impression that you wanted to draw data from several different data sources and put the results into a cursor with a common structure. I'm sorry if I didn't understand your problem...

I was pre-understanding I was talkin about parameterized views <g>