Eric,

Just curious as to why you do not edit records in a grid?

>Well, yes it does. If you are in the middle of editing records at the time you want to change the order of the table you have a problem. It depends on the form design and where the editing is being done as far as making sure the grid reflects the actual order of records at any given moment in time. One other way of "refreshing" a grid is
>
>

>thisform.grid1.recordsource = ""
>thisform.grid1.recordsource = "mycursor"
>thisform.grid1.refresh()
>

>
>somewhere after you change the values in the order field. This may or may not work depending on what other things may be taking place.
>
>BTW, I never edit records in a grid.
>
>HTH
>
>
>>Eric,
>>
>>Doesn't that defeat the purpose of using 'buffering'?
>>If I update the table then I can't do a revert and I have undo the users changes via code.
>>
>>>>I have a grid in VFP5 which uses a free table (alias) as its source.
>>>>The buffer override is '5' - optimistic table buffering.
>>>>This alias is opened in the environment with an order.
>>>>One of my command buttons on the same form is 'move down' which basically moves this record down and the following record up in the grid. This is done by replacing a field on both records which is also the order of the table.
>>>>I have tried refreshing the grid and the form, however, the grid is still displayed in the original sequence. I know that the records have actually switched position because I have browsed the table in the command button.
>>>>When I modify the buffer modem override in the environment to '0' - no buffering, the data in the grid is displayed properly.
>>>>Thank you for any assistance.
>>>
>>>You probably need to issue a tableupdate() since your data is buffered.