How to handle large result sets - InfoPath Dev
in

InfoPath Dev

How to handle large result sets

Last post 08-01-2005 11:54 AM by bobstery. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-28-2005 02:23 AM

    How to handle large result sets

    Is there anyway of only returning the top 50 rows from a query, but giving the user the option to ask for the next 50 when required, using SQL server and a view?

    I know I can use the top statement in SQL however I need to make this dynamic i.e. user clicks on a button and requests rows 0-50, 51 to 100 etc.

    I know Infopath is really slow when returning large result sets, and therefore I need to only show a small segment at a time.

    Many Thanks
  • 07-28-2005 10:44 AM In reply to

    Re: How to handle large result sets

    Hi bobstery,
    Even we had similar problem before. Its not the datasets that make InfoPath slower,
    To counter that you can have the data in the memory but not show full data in the UI. For this you need to have two datasets, one which is binded to the UI another which will provide data to the first dataset.

    We are comming up with a tips and tricks document by this monday which will adress this issue. So wait for that if you dint understand my above solution.


    Agni
    InfoPath Dev India
  • 08-01-2005 11:54 AM In reply to

    Re: How to handle large result sets

    Many Thanks I look forward to the document.
Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.