Prologika Forums

I have created a "parent" table with x columns and added an extra detail row to drop a nested subreport into the table passing parameters into the sub in order to obtain the child subreport. The problem is that the the while I can line up the columns in the sub report with the parent report,

I observe something like this:

parent columns:

a  b c d e f

child columns

a b c d e f

The problem is in the last column of the parent "f" it appears stretched out for some reason-about an inch even though can grow is set to false.

Its like the child is forcing the parent's last column to expand yet when i observe the border around the table in the child it is clear it is fitting in the "original" boundry(layout view). Yet on preview mode, the parent's last column is extended width. Note I tested it with No data in the child's last column and it still expands the parent column by that inch.

Also note when I dropped the subreport into the parent report I'm merging the cells on the detail row that the subreport fits into across columns a, b, c, d, e, f.

So even though the subreports data lines up properly under a, b, c, d, and e; f still expands outward.

Any clues or suggests on what I should consider changing. I'm stumped.

I've also tried hiding that buffer column "f" in the parent, after which that extra inch gets applied to column e and I'm right back to where I started...

Do both reports have the same body width, page width, and and margings? Does it help if you enclose the table in a rectangle? Can you submit an isolated test harness?

I think I found the source of the strange behavior. they were both the same but there was a visiblity expression on one of the columns... and even though that same expression was in the sub and the same parameter used in the parent passed into the sub and applied to its hidden column expression, the combination of the nested sub report forces the last column in the parent over the same distance of the so called hidden column. we end up with col a b c d e f + c's width where c has a visibility expression on it.... strange!

Bottom line is to avoid spanning your subreport over columns on the parent that have hidden expressions. This may mean multiple subreports...

I do wonder how a person would ever handle a conditionally hidden column that appears on both parent and sub but for now I won't cross that bridge.

Sounds like an issue with the renderer. You may want to report this on connect.