James

I'd say, in essence, whatever change in underlying data causes the grid to need to be refreshed (e.g. with new child data) - have that in one form method only. So whichever sequence of pages is clicked on it won't matter, so long as whatever action that causes the grid re-popn. has been enacted.

When the grid cursor is built, end with a LOCATE so you're not at EOF (which rings a bell, actually: You sure the data aren't there in the grid but the grid's scrolled down past them? That baffled me for a while once)

Terry

>This is a question that has been asked and answered before, but I don't seem to have any of the circumstances noted before.
>
>I have a pageframe, with grids on multiple pages. Each grid is rebuild from scratch (that is, the grid is created, the columns are all added programatically, and the recordsource assigned) when its page is activated.
>
>It appears that if the pages are visited in a particular order, some of the grids may not display any records. Now, I hasten to say, I can verify that the alias for the grid exists, has records, and is unfiltered; that the recordsource for the grid is correct; and that all the columns exist (their headers appear correctly, just no records) and have the correct controlsource.
>
>This doesn't appear to be just a matter of avoiding grid reconstruction, since I consciously build the grid and its columns as I need to.
>
>Any suggestions as to what might be causing this?
>
>TIA,