Yes, table buffering is on both my employee table and the transaction table. There is a tableupdate in the save process. I was really suprised at the record showing up at the bottom, too. Verry odd. The stuff in the grid has an index on the employee's ID and then the date/time of the transaction so as to put the records in chronological order.

Thanks,
Don

>>I sort of tried that, except that I didn't use the form property and I didn't have the goto in the refresh of the grid. I had a save button that I tried recording record pointer doing a refresh setting focus etc. But it didn't work. Do you think if I put the goto in the refresh of the grid that it would make a difference?
>
>No, cos then every time the grid refreshed, it would be going to the stored rec #??? Besides, I'm not sure that wouldn't replace the native behind0-the-scenes code for the method, thus disabling it (refresh is a method, not an event). No, I say put that code just after the record saving code, i.e. outside the grid., but you say you've tried that.
>
>Is there any buffering in place on the xaction file? Is it TableUpdate()ed and at what point.
>
>There could be a host of reasons whyt this is happening. Personally I'm surprised that you see the new record at grid bottom, if the grid is ordered on a key (it IS isn't it?)
>
>>
>>Thanks,
>>Don
>>
>>>>I'm having a tough time with a grid on a form. This form and grid worked fine in VFP 8 but since we moved it to VFP 9 it's not working properly. We have a screen based on an employee table with a grid that has child data in it (transactions).
>>>>
>>>>The transactions in the grid are ordered chronilogically and all that seems to work great. I add a record to the transactions table and no matter what date time I use it appears at the bottom of the grid. So let's say I use some date and time that should land somewhere in the middle of the data (that I would need to scroll up in the grid to find if it were in the right place). If I try to refresh it does nothing, my new record stays at the bottom. If I try to setfocus() on the grid, the grid re-orders correctly but the record pointer is still on the last record and now I have to scroll up to find my new record I just added.
>>>>
>>>>Both employee and transaction tables are VFP 9 tables. I'm wondering if this is a bug in VFP 9?
>>>>
>>>>Thanks,
>>>>Don
>>>
>>>How about:
>>>
>>>As soon as you've finished creating the new rec, store it's RecNo() in a form prop. Refresh the grid, and/or Setfocus on it and Goto the stored rec #.