That's what I'm in the process of trying.

Thanks,
Neil

>Remove the relation from the DE of the form. Then set it in the load event of the form manually with code.
>
>>Yes, I'm refreshing page 2.
>>
>>The relation is the problem. Watching the session window with the form running shows no relations between the tables, even though the relations are set in the data environment of the form. (Opening the data environment of the form shows a line from the 'ceeb' field in the parent table to the 'ceeb' index of the child table. One to many property is set to .T..
>>
>>If I issue a SET RELATION and SET SKIP command in the command window (or set the relations in the session window) while the form is running, it behaves properly. It seems that the relation that is set in the form's data environment is not being engaged.
>>
>>Any other ideas?
>>
>>Thanks,
>>Neil Preston
>>
>>
>>>Are you refreshing page2 when you switch to it?
>>>If you put SET STEP ON just after switching to page2, then look at the relation between the two tables, is it still correct? Are the record points on the proper (and the related) records in both tables.
>>>
>>>>Page one has several text boxes used for entering search parameters. A Search button gathers the search values and constructs the parameters for a locate command. (Several fields are not indexed, and don't need to be for the main application.) When the search is complete, it switches to page 2 and displays the results. On page two, I included some fields from the second table, which won't display the related data.