If your DE has the relationship defined already, then you don't need to reposition the record pointer in the child table. Just move the record in the parent table then refresh the form. The child recs will display.

To ensure all is fine, put a SET STEP ON just after you move to the next record and after you refresh the form. You can then check to see if all tables and record pointers are all okay.

>Yes, I'm sure I'm doing this in an awkward way. Paramaterized Views would be ideal. However, rather than reworking the code, I'd rather slap a fix on my Kludge.
>
>My DE has a mother-daughter relation with invoice1 and invoice2. Invoice1 is the billing info, Invoice2 are the line items. They are related by invoice number.
>
>Now, if I don't move the record pointer to a different invoice number prior to appending records to a new invoice through my form, everything is fine.
>
>But, if my order entry person goes to a previous invoice number, then that previous invoice's line items shows up in the grid instead of the appended records.
>
>Just before I code the grdbase1.refresh, I make sure the record pointer is in the proper place.
>
>Select Invoice1
>seek lcInvoiceNo
>sele Invoice2
>seek lcInvoiceNo
>thisform.grdbase1.refresh()
>
>Do I need to refresh the individual columns of the grid instead?