Parent-child table combinations showing final child entry twice
Posted: Wed Jun 20, 2012 9:26 am
Hallo Support,
I have a strange phenomenon for which I cannot find an explanation, despite extensive testing. I am using parent-child tables and am getting the problem that the final entry in each child table is being displayed twice, as in the screenshot here.
On the left, you see "PEK", which is the final parent entry for the left table. Then comes the final child entry, starting with "Pflegekostenversicherung...". This entry is then repeated for reasons unknown to me. As I have carefully checked all "Can Break" and "Keep Details Together" properties etc. and nothing makes a difference, I can only assume that something internally is not quite right.
Now the really strange thing: in screenshot #2 you see a part of the xml data file (in the zip attachment). If you set 1 then the first page of the report is displayed and you can see the problem as described above. If you then set 2, the second page of the report is then enabled and the problem disappears, everything works fine, although the databand and table definitions look exactly the same! The attached mrt is a simplification of the report I am using. I've reduced everything to a minimum to show the problem.
I'd be grateful for any help you can give me on this as we plan to go live with it at the end of the month.
Best regards,
John Kitching
I have a strange phenomenon for which I cannot find an explanation, despite extensive testing. I am using parent-child tables and am getting the problem that the final entry in each child table is being displayed twice, as in the screenshot here.
On the left, you see "PEK", which is the final parent entry for the left table. Then comes the final child entry, starting with "Pflegekostenversicherung...". This entry is then repeated for reasons unknown to me. As I have carefully checked all "Can Break" and "Keep Details Together" properties etc. and nothing makes a difference, I can only assume that something internally is not quite right.
Now the really strange thing: in screenshot #2 you see a part of the xml data file (in the zip attachment). If you set 1 then the first page of the report is displayed and you can see the problem as described above. If you then set 2, the second page of the report is then enabled and the problem disappears, everything works fine, although the databand and table definitions look exactly the same! The attached mrt is a simplification of the report I am using. I've reduced everything to a minimum to show the problem.
I'd be grateful for any help you can give me on this as we plan to go live with it at the end of the month.
Best regards,
John Kitching