System.ArgumentOutOfRangeException on grid.Redraw = True -Flex Grid 10.0.20252

Posted by: santer.p75 on 16 July 2026, 12:42 pm EST

  • Posted 16 July 2026, 12:42 pm EST

    Hello,

    I’m going to try again…

    When I have a Flex grid with calculated footers, I frequently encounter an error. It’s not reproducible, but it happens all the time—I haven’t figured out why.

    I’ve been waiting for a solution since December, but support is ignoring the problem. Maybe someone else has the same issue?

    The error is always triggered by

    grid.Redraw = True
    .

    I set

    grid.Redraw = False
    , populate a few hundred rows, and then set
    grid.Redraw = True
    . Most of the time the error occurs, but not always.

    System.ArgumentOutOfRangeException

    HResult=0x80131502

    Nachricht = Index was out of range. Must be non-negative and less than the size of the collection. (Parameter ‘index’)

    Quelle = C1.Win.FlexGrid.10

    Stapelüberwachung:

    bei C1.Win.FlexGrid.C1FlexGridBase.m_dm(Point a)

    bei C1.Win.FlexGrid.C1FlexGridBase.m_dl()

    bei C1.Win.FlexGrid.C1FlexGridBase.get_RightCol()

    bei C1.Win.FlexGrid.C1FlexGridBase.Invalidate(CellRange rg)

    bei C1.Win.FlexGrid.C1FlexGrid.Invalidate(CellRange rg)

    bei C1.Win.FlexGrid.C1FlexGridBase.m_aa()

    bei C1.Win.FlexGrid.C1FlexGridBase.OnGridChanged(Object sender, GridChangedEventArgs e)

    bei aq.m_bm(GridChangedTypeEnum a, Int32 b, Int32 c, Int32 d, Int32 e)

    bei aq.m_bm(GridChangedTypeEnum a)

    bei bc.m_c(C1FlexGridBase a, CellRange b, Boolean c, Boolean d, Boolean e)

    bei bc.m_r(GridChangedTypeEnum a)

    bei aq.m_bm(GridChangedTypeEnum a, Int32 b, Int32 c, Int32 d, Int32 e)

    bei C1.Win.FlexGrid.RowColCollection.m_l(GridChangedTypeEnum a, Int32 b, Int32 c)

    bei C1.Win.FlexGrid.RowCollection.m_m(Int32 a, Boolean b)

    bei C1.Win.FlexGrid.RowCollection.m_l(Row a, Boolean b)

    bei C1.Win.FlexGrid.C1FlexGridBase.m_bk()

    bei C1.Win.FlexGrid.C1FlexGridBase.m_bj()

    bei C1.Win.FlexGrid.C1FlexGridBase.m_bh()

    bei C1.Win.FlexGrid.C1FlexGridBase.EndUpdate()

    bei C1.Win.FlexGrid.C1FlexGridBase.set_Redraw(Boolean value)

  • Posted 17 July 2026, 7:45 am EST

    Hello,

    We completely understand your concerns and apologize for all the inconvenience this has caused. Please be assured that we are not trying to ignore your issue. Part of the issue was resolved in the 2025v2 Hotfix 2 release; however, it appears that you are still experiencing it in certain scenarios. Since we have not been able to reproduce the issue, it is difficult for us to investigate it further without a sample project or clear steps to reproduce the problem.

    Could you please provide the following information:

    1. Is there any specific action your users perform in the grid that leads to the exception?
    2. Is this the same grid for which you reported the previous issue?
    3. Is the issue tied to a specific environment or system? If so, could you please share its details?

    Also, did you try the workaround we shared in your support case (CAS-60608-C2F4R6), where we suggested overriding the method and wrapping it in a try-catch block?

    For further investigation, we kindly request that you provide a project that reproduces the issue, even if it is your main project as you shared previously. This will help us investigate the issue further.

    In the meantime, we have shared the stack trace with the development team to see if they can provide any insights into the error. We will let you know of any updates as soon as we receive feedback from the team.

    [Internal Tracking ID: C1WIN-35261]

    Regards,

    Uttkarsh.

  • Posted 22 July 2026, 8:10 am EST

    Hello,

    As already mentioned in response to case (CAS-60608-C2F4R6), this doesn’t help.

    I’ve since received a tip from another developer, and it seems that this change is currently working.

    Before each call of redraw and Rows.Count, I set Row=0 and RowSel=0.

    Regards

  • Posted 23 July 2026, 6:07 am EST

    Hello,

    Thank you for sharing the workaround you are currently using to prevent the exception. We have shared this detail with the development team, as it may help with further investigation. We will let you know as soon as we receive any update.

    Regards,

    Uttkarsh.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels