Hi Curtis,

I've always used cursors to populate grids, and that too, setting the grid's RecordSource only after instantiation, say in the Init() event of the container for performance purposes. Apart from that, it gives you the flexibility of filtering data (through parameterised queries) on the fly, since filtered record sources for grids seriously impact performance again.

Also, the source name (your named cursor) remains consistent with each re-run of the SQL to create the cursor. You just need to refresh the grid, and bingo.

Cheers,




>I'm using about 4 grids on separate page frames, each filtered to show different information from the same table.
>
>When using views - to requery the view, I have to re-use it or (recreate it, which seems to create another table) and neither method repopulates my grids.
>
>Do you have any suggestions as to the use of Views Vs Cursors from local tables? Which is best when?
>
>Thanks again,
>-Curtis (I work for Jim)