Given a grid with customized properties that is based on a cursor, I have found with VFP 5.0 that using the workaround:

Grid.Recordsource=""
SELECT blah blah into the cursor the grid uses
Gris.Recordsource=cursor_alias

will no longer protect the properties of the grid columns. In particular, the controlsource for each column is reset. Unless the columns in the grid happen to exactly match the order of fields in the cursor, the grid will display the wrong info in its columns. Look at KB article Q140653 for MSFT's suggestion . Does anybody know a way to work around this problem without creating a tempory dummy cursor like MSFT suggests? What I cannot believe is that MSFT says this behavior is by design. Basically what it means is that you've got to do a stupid juggling act. I don't understand why there isn't a built-in method that lets one recreate a grid's cursor on the fly without destroying critical properties of the grid.