|
Re: Size of .rptdocument [message #975359 is a reply to message #973870] |
Wed, 07 November 2012 20:29   |
|
The report document will contain all the data needed to render your report, based on your design. Nested tables and such will increase the size. If you can attach your design, I might be able to point out some stuff you could do to improve this.
Michael
Developer Evangelist, Silanis
|
|
|
|
Re: Size of .rptdocument [message #982378 is a reply to message #977492] |
Tue, 13 November 2012 05:02   |
|
I may have found an issue. You have a few data elements bound to the same dataSet that is used for the outer table. This may be causing part of your large .rptdocument issue. If there isn't a reason for this, you might try removing the dataSet binding from these individual elements and let them inherit from the table.
PS_NAME, PS_TEL, and PS_FAX
Let me know.
Michael
Developer Evangelist, Silanis
|
|
|
|
Re: Size of .rptdocument [message #986027 is a reply to message #985916] |
Sat, 17 November 2012 18:16   |
|
The bindings I listed are in the only dataSet you have, which is the same table that is bound to the table. When you drag a field over, into a table bound to the same dataSet, already, it doesn't list bindings, in the binding tab. If you click on the data elements, in your design, that I listed above, you'll see that they are individually bound to the dataSet. Try setting these elements to have no dataSet. This will cause them to inherit from the table.
Michael
Developer Evangelist, Silanis
|
|
|
|
Re: Size of .rptdocument [message #986559 is a reply to message #986451] |
Tue, 20 November 2012 23:07  |
|
It would have been running the embedded dataSet for each group. So, however many groups there were. And yours was in group2, so it would have been however many group two elements there are for each group1 value, added together.
Michael
Developer Evangelist, Silanis
[Updated on: Tue, 20 November 2012 23:10] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.02274 seconds