Hi Terry,

Thanks again for your help on this one. I'm not using DE. I'm using the LinkMaster and ChildOrder props on the grid to control the relationship. Relationship works good as I move from one employee to the next, it only shows the transactions for that employee. So that part is working pretty good.

Thanks,
Don

>OK Don
>
>I don't know how you're controlling the relationship of the parent and the grid. Did you drag the tables into the DE and leave their relns alone?
>
>As you change an Emmployee does the grid change to show only the xactions pertaining to the employee?
>
>If so, what I do is: in the DE delete the reln arc (which points from the xaction table, Employee FK to the employee table Employee PK. Then describe your own, the opposite way round, temporarily making the employee table point to a "fan out" of xactions.
>
>This does not affect the permanent relns in the dbc.
>
>Make a back-up of your form first and try this. You may have to get rid of grid-controlling code that you've put in.
>
>>It's a table. I have a form with this grid that is basically based on two VFP tables. A parent table and a child table with a one to many relationship. The parent table has employees and the child table has transactions.
>>
>>Thanks,
>>Don
>>
>>
>>>What do use as a grid recordsource? You said you show child records there, so it's a cursor?
>>>
>>>>I tried the SEEK and I also tried with a GOTO but it didn't seem to work. The record pointer would stay at the bottom of the grid. If you suspended the program and looked at the table the record pointer had moved to the appropriate record but on the screen it was still showing the last record in the grid? I thought I should be able to just refresh the grid, but that didn't seem to help.
>>>>
>>>>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
>>>>>
>>>>>Could you just SEEK the record and then SetFocus to grid. That's normal way.