I had this problem several years ago with VFP3. I solved it by never printing a report from the original tables but always making a 'report cursor' with both parent and child fields. Since the cursor is temporary it doesn't waste disk space and you no longer need to worry about Set Relation, Skip, etc. The problem with my VFP3 app seemed to be with my Set Relation code.

There are several recent threads in the Reports & Report Designer area on the advantages of a report cursor and how to get all your data into it.

HTH
Barbara

>I just discovered an anomaly with one of my reports. In the program, I give the user the option of sending the
>report to the screen or the printer. If they choose to send it to the screen to preview it and then send it to the printer
>or scroll to the second page and back to the first page, the data on the first page is changed (and therefore, is incorrect).
>If they send the report directly to the printer it is ok. Has anybody experienced this or have any suggestions as to
>what is going on and how to fix it?
>
>Thanks,
>Rena