A common question is "How do I implement paging within a Repeater?" Although the beauty of the Repeater control is its flexibility, you're on your own for building most functions. ASP.NET 2.0 has included some new controls that provide paging, as does the DataGrid in ASP.NET 1.1. However, this tip shows you how to roll your own paging for a simple data viewer.
public partial class PagedRepeater : System.Web.UI.Page
public int PageNumber
if (ViewState["PageNumber"] != null)
ViewState["PageNumber"] = value;
protected override void OnInit(EventArgs e)
protected void Page_Load(object sender, EventArgs e)
private void LoadData()
SqlConnection cn = new SqlConnection("your connection goes
SqlDataAdapter da = new SqlDataAdapter("your query goes
DataTable dt = new DataTable();
PagedDataSource pgitems = new PagedDataSource();
DataView dv = new DataView(dt);
pgitems.DataSource = dv;
pgitems.AllowPaging = true;
pgitems.PageSize = 25;
pgitems.CurrentPageIndex = PageNumber;
if (pgitems.PageCount > 1)
rptPages.Visible = true;
ArrayList pages = new ArrayList();
for (int i = 0; i < pgitems.PageCount; i++)
pages.Add((i + 1).ToString());
rptPages.DataSource = pages;
rptPages.Visible = false;
rptItems.DataSource = pgitems;
void rptPages_ItemCommand(object source,
PageNumber = Convert.ToInt32(e.CommandArgument) - 1;
<%@ Page Language="C#"
<asp:Repeater ID="rptPages" Runat="server">
<table cellpadding="0" cellspacing="0" border="0">
Runat="server"><%# Container.DataItem %>
<asp:Repeater ID="rptItems" runat="server">
<li><%# Eval("pkItemID") %>: <%# Eval("Description") %></li>
The page uses one Repeater for the page numbers and a second one for the items. This example shows items from a product catalog, but any database table will do. To start, create a ViewState property (see the previous tip) to store the current page number. This property also is coded to return a zero, which is the first page number (at least as far as the database is concerned).
When the page is first loaded, the code calls the LoadData routine, which gets a DataTable containing the records. Then, that is connected to the PagedDataSource class by way of a DataView object. The DataView also can provide sorting; this makes it easy to allow users to sort by a particular column heading. You simply create another ViewState property and store the sort field at this point.
The example has a page size of 25, which is put into the PagedDataSource object. Based on the number of rows, the PageCount property is populated with the total number of "pages" in the data source. The code forces the CurrentPageIndex to the default page number of zero, which positions it at the first record on page 0. The other bonus to the PagedDataSource object is that it will give back only 25 records, which means you don't have to keep count or manually bind it to the item list repeater. This is a nice change from the code you may have done in ASP to perform this same function.
Next, the example needs to build the page number list; the code does this with an ArrayList holding each page number as a string. Note that the example adjusts the page number up by one because the average person doesn't understand that page zero is the first page—the user will see page 1 as the first page.
The example wires up an event handler to respond to the clicks in the paging repeater next. It converts the CommandArgument and subtracts one from it because it's showing the value in the repeater as one more than the actual page number. Calling LoadData repositions the list to the appropriate page.
The result is a list of pages above a short item list that changes as the user selects different pages. This model can be expanded, as previously mentioned, to support a user-selectable page length or sorting options. However, if you change the page size, be aware that the number of pages will change and the previous page number may be invalid. The PagedDataSource won't generate an error if you pick a CurrentPageIndex outside the valid range, but you should be sure to trap for this condition anyway.