I guess this is because grid controls a lot of things related to the control inside of the column. As a result it is preferred to work with it through column instead of directly - direct work with control might cause breaking relation with a grid and as a result - some side effects.

>I think that I have worked out this specific problem, however, I do not understand the reasoning behind it. When the user clicked on 'add' a grid row, I was refreshing the grid and doing a setfocus to the 'text1' property instead of the column property. When I modified the code to setfocus to the column property the problem did not occur. Is there a reason for this?
>
>>Hi!
>>
>>No, it is not a bug, it is bad refreshing of the grid after adding a record. usually behaviour depended on the code you run inside grid events or methods, and sequense of actions. After adding new record Grid.Refresh should be enough to fix a problem. Try it and let us know if it solved the problem. If not, then provide more information to do further investigate of the problem.
>>
>>>I have been having problems with errorenous data populating grids after modifying a form in VFP5. Has anyone else observed this behavour?
>>>The source of the grid is an alias and all of the control sources have been defined properly.
>>>I modify a control on the form such as a command button which is not in the grid.
>>>I start my application (withoug quiting VFP), select my form from the menu and start adding records to the grid.
>>>On a random basis, data from the same field in another record in the grid displays on the row that I am adding.
>>>If I quit and restart VFP after modifying the form the above problem does not occur.
>>>Is this a documented bug that I am not aware of?
>>>TIA.