Strongly typed dataset issue

Posted by: j2associates on 8 September 2017, 1:33 pm EST

  • Posted 8 September 2017, 1:33 pm EST

    Hello all,


    We have a strongly typed dataset that is loaded from a very large xml file via a schema. As you can see from the attached screen shots, the vertical scroll bar always shows at 100%. As you enlarge the screen, more and more rows become visible but when you have enlarged the form as large as you can, it is impossible to scroll the spread.


    The project uses 4.0.2001.2005 with .Net Framework 2.0. The same behavior is exhibited by 4.0.2003.2005. Version 4.0.2005.2005 displays the scroll bars more correctly but there is a lot of flicker as the screen is painting. If you click the down arrow on the vertical scroll bar it throws an Unhandled ArgumentOutOfRangeException with the following message:


        Invalid row index specified (must be between 0 and 0).
        Parameter name: row
        Actual value was 1.


    I have attached screen shots showing the issue as well as a project that you can use to reproduce the behavior I am seeing. Thanks in advance for any ideas and/or suggestions!


    2008/10/StronglyTypedDataSetIssueScreenShots1.zip
  • Replied 8 September 2017, 1:33 pm EST

    ScreenShots2.
    2008/10/StronglyTypedDataSetIssueScreenShots2.zip
  • Replied 8 September 2017, 1:33 pm EST

    Project.
    2008/10/StronglyTypedDataSetIssue.zip
  • Replied 8 September 2017, 1:33 pm EST

    Hello,


    This is correct behavior. The scrollbar does not scroll per pixel, but rather per row. Since you only have one row, there is not another row at the parent level to scroll to.

  • Replied 8 September 2017, 1:33 pm EST

    Thanks for the explanation! Any workarounds other than appending a blank row?

  • Replied 8 September 2017, 1:33 pm EST

    Hello,


    There is not going to be a way to do what you want with the layout you have. Adding a row will allow you to scroll to the next row, but you will still miss all the data (in the child rows) that you can not see now.The only ways to fix this is to have less relations between the parent and children table. Or by using more than one Spread control.

Need extra support?

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

Learn More

Forum Channels