BuyLog In
Bug Report Q478363
Visible to All Users

Composition Report Link - The "Index out of bounds" exception occurs when building the report link whose StartEachItemFromNewPage property is set to False if the composition includes a report link with no pages

created 12 years ago

I have a composite report link with 7 grid report links linked to it.

Each of the 7 grid report links are linked to a grid with a single table gridview, in unbound mode. (Each grid appears in a tab of a page control).

When I print the report all is well when all of the gridviews have at least one row in them. However, if a gridview has no rows an exception is raised in

TdxPSCompositionReportRenderRowInfo.CalculateContentInfo

It is trying to access PageRenderInfo[0], which does not exist (presumably because the gridview has no rows).

I have attached a text file with two sections of information.

The first is text from the DFM which lists the properties of the TdxComponentPrinter, the TdxCompositionReportLink, and the linked TdxGridReportLink components.

The second is a madExcept bug report including a stack trace of the program.

Show previous comments (1)
JF JF
John Furlong 12 years ago

    I have reproduced the problem.
    The following properties must be set as indicated:
    The TdxCompositionReportLink's StartEachItemFromNewPage property must be set to False.
    The TdxGridReportLink's OptionsLevels UnWrap Property must be set to True.
    The TdxGridReportLink's OptionsLevels SkipEmptyViews property must be set to True.
    I have attached a modified sample project.

    DevExpress Support Team 12 years ago

      Hello,
      We appreciate your valuable research. I have reproduced the described behavior and forwarded this ticket to our developers for further investigation.

      JF JF
      John Furlong 12 years ago

        Just to let you know, I have worked around this by setting SkipEmptyViews to false. I don't need an urgent fix.

        Sign in to comment on this post

        Answers approved by DevExpress Support

        created 12 years ago (modified 12 years ago)

        We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

        Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

          Sign in to comment on this post

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.