Hi John,

This did turn out to be a "low cost" solution and it did solve the problem. A couple of things I did (in case someone else finds this thread) is to set .Tabstop to .F. and .ReadOnly to .T.; found out though is stops working if a RETURN .F. is put in the .When() method (I guess its possible VFP skips the focus if .When() returns .F.). Overall, solved the problem. It is funny that there is a problem with this grid when in all other cases, I have not seen it. The only real difference is that the grid holds very few records typically and it is small overall. When debugging, the records are in the cursor that is bound to the grid - you can see them via the debugger. But the grid is actually blank.

Anyhow, problem solved and customer will be happy.

Thanks again. And whoever else suggested this, thanks also.

Albert

>Hi Albert,
>
>This was all done years back, so recollection shaky- but it was to do with resequencing or refreshing after recno() change while the grid has focus. I recall that the grid could go "blank" after a drag-drop meaning no visible content intermittently, or selected row might jump despite explicit GO to maintain current record, or various other anomalies especially if you need to SCAN or locate in the recordsource whenever edits are made. Moving focus elsewhere and then restoring after everything finished, seems to have prevented these glitches. This doesn't seem to be reported by others but if grid refresh anomalies are experienced, losing and restoring focus may be a very low-cost experiment/remedy.