SQL Database Integration

Re: AllowPaging

nthaka1 — Mon, 12 Apr 2010 13:59:03 GMT

Kalyan.

We want the code to implement paging in InfoPath not in ASP.NET.

Any one having knowledge of this functionality please send some steps to implement it.

Thanks.

Re: AllowPaging

Kalyan Gaddam — Mon, 03 Jul 2006 13:12:47 GMT

Hello
Welcome to Infopathdev Forums

Please read the links below. It has code which explains to do paging for data in SQL database and Asp.net
http://www.codeproject.com/aspnet/dbpaging.asp
http://134814.datagrid.codebetter.com/blogs/jeffrey.palermo/archive/2005/11/18/134814.aspx

I hope these will help you.

Re: AllowPaging

binay_93@hotmail.com — Mon, 03 Jul 2006 12:23:24 GMT

Hi,
please send me code sample as how to dopaging using infopath.however one sample example of master detail paging is there but i need to know if i am retrieving large data from database how can we perform paging using next/prev button.

Thanks & regards
Binay

quote:
Originally posted by maulik

As a developer, this is not a good idea to have next/prev button controlling queries to a db.
Also, in a real world scenario, this could become a drag on performance on the DB Server.
Most prev/next functionality should be handled by the client, for example, the scroll bar. What you see is only a finite number of rows, the rest is in the client data memory area. Imagine if it were to query the DB.

Re: AllowPaging

binay_93@hotmail.com — Mon, 03 Jul 2006 12:02:26 GMT

Hi,
I very new to Infopath 2003
please anyone send me the code as if how to do paging using prev.next button if there is large data we are retrieving from database.

Re: AllowPaging

Patrick Halstead — Tue, 10 May 2005 01:31:52 GMT

Hi Maulik,
I agree with your post on next/prev. However, InfoPath has serious perf issues when you a) load lots of data into the main DOM, and b) bind it to your view. My suggestion would be to use views or filtered queries to reduce the data set. If that isn't an option, load the data into a secondary data source (secondary DOM) and show a small window onto your data from the view (or copy a limited amount to your main DOM and use some kind of scroll paging there).
Good luck,

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: AllowPaging

maulik — Mon, 09 May 2005 21:53:46 GMT

As a developer, this is not a good idea to have next/prev button controlling queries to a db.
Also, in a real world scenario, this could become a drag on performance on the DB Server.
Most prev/next functionality should be handled by the client, for example, the scroll bar. What you see is only a finite number of rows, the rest is in the client data memory area. Imagine if it were to query the DB.

Re: AllowPaging

Greg Collins — Wed, 19 Jan 2005 02:00:32 GMT

It might be best to have a next/prev button set which requeries the database based on a starting and ending row. This will reduce the amount of data actually in the form at one time which should prevent any performance issues.

Greg Collins [InfoPath MVP]

AllowPaging

liuqian — Tue, 18 Jan 2005 01:42:05 GMT

Oh,When i display a lot of data from database use reports table,it's very long .Can reports table like asp:dataGrid have AllowPaging property ?
Please tell me. Thanks.