>Hi Harry ----
>
>I must be missing something: Why are you messing around with the recordsource?

it follows on from many previous threads where users have found that clearing the recordsource and resetting it after your changes apparenlty solves some grid display problems when the datasource disappears from under the grid. It was the solution to a problem I had many moons ago so it was a distinct possibility that it might work for this one too. Now - whether and why it should work, don't ask me! I'm just a sophomore on vfp, I just do what I'm told ;-)

>>I would design it this way: Put the table in the DataEnvironment of the Form with the Grid.

tried that. No difference

>> Set the RecordSource at design time;

it is...

>>don't mess with it at run-time.

see above - it does solve some problems.

>>Set the Form to a Private DataSession. In the detail entry form, do NOT open the table:

tried it. No effect - but see my comments elsewhere about getting the same lack of display from a simple button doing an append and stuffing some junk values just for display purposes. (Even without leaving the grid form It still wont display the appended record, even though I can click on the dataentry button and go and see the values of the appended record.

>> Set the DataSession to Private. This allows it to "inherit" the parent form's datasession.

tried that and still no display.

>> I am assuming that the Save button is on the child? If so, TABLEUPDATE() the table (if buffered) and close the form. If you Refresh() the parent, the new record will appear.

no, there is no save button in that sense. (Its not necessary). The 'Save' refers to saving an entire journal which may consist of several dozen or even hundreds of records.


Thanks

Harry