My guess is that you've got indexes on the field(s) in question as well as having the order set to same. Changing the values of indexed fields in a Grid can cause rows to "fly away".

Try setting to "no order" in the Grid and see what happens.

Also, when you say "SQL table", do you mean the table was generated from a SELECT ? If that is so, and this is only a filtered table in a multi-user environment, it could be acting up due to multi-user updates. You could try forcing the table to a physical cursor if that's the case and then seeing what happens.

Grids can act up but I have yet to find any behaviour that cannot be explained.

>I'm at a loss as to how to describe this but I'll try: I have a grid containing a couple of fields of information from a SQL table and a logical field that allows the user to check a box to select the row for inclusion in another process. Ideally, the SQL data would be read only and the column with the checkbox and caption (sparse = .f.) would be editable. The problem is that the user can select the first row using the mouse but when he tries to select another row, the data in the grid scrolls without warning, usually leaving the user at end-of-file after having checked the wrong row. It's something straight out of Whil Hentzen's "User Hostile Interface" demo. What is going on?
>
>FWIW, the method code does not use setfocus(), the recordsource is a temporary table, and in the worst case, there are up to 40 records, only 8 of which will display in the grid at one time. This seems to be similar to the problem I posted several months ago about the elevator or thumb on the vertical scroll bar moving erratically in the grid when there are more rows than will display at one time, always returning to beginning or end of file. That problem still has not been solved. Both problems may be symptoms of a major "infelicity" in the grid but if so, it seems to make it totally useless. I'm hoping I've missed something very obvious...