The "safe select" is the easiest and best way if the amount of data is small to moderate using your current setup.
If you have huge data sizes in the gridcursor, the double reading will create a lag.

Cursoradapter.Refresh will allow you to keep the grid - allows any data size, but perhaps some retooling is needed.
You might get away with slapping your current SQL into .SelectCmd and fill a few other properties dynamically.

If you need to keep your SQL with huge data sets, unbind the grid and rebind later,
taking care to also save formating properties of the grid columns.
There are some issues with grid code - works best if no code is in the grid class.
And rethink your logic, as SQL reading large sets should be avoided <g>

regards

thomas