Addding Paging to a Repeater Control

Hi All,

I believe I have closely following the following article to implement paging for a Repeater control but for some reason it doesn't seem to be paging to the next set of data.

http://aspnet.4guysfromrolla.com/demos/TestRepeater.aspx

My code is as follows... can anyone see anything that could be wrong?...

The only differences between the 2 are my datasource is a SQL database called by SubSonic and my object variables have different names...
<h1>Product Search Results</h1>
<table width="100%" border="0">
   <tr>
      <td>  Repeater control with Paging functionality</td>
   </tr>
   <tr>
      <td>  <asp:label id="lblCurrentPage" runat="server"></asp:label></td>
   </tr>
   <tr>
      <td>  <asp:button id="cmdPrev" runat="server" text=" << "></asp:button>
          <asp:button id="cmdNext" runat="server" text=" >> "></asp:button></td>
   </tr>
</table>
<table border="1">
   <asp:repeater id="repeaterItems" runat="server">
      <itemtemplate>
         <tr>
            <td>  <b><%# DataBinder.Eval(Container.DataItem, "ProductTitle")%></b></td>
            <td>  <b><%# DataBinder.Eval(Container.DataItem, "ProductRef")%></b></td>
            <td>  <b><%# DataBinder.Eval(Container.DataItem, "Price")%></b></td>
         </tr>
      </itemtemplate>
   </asp:repeater>
</table>
 
 
 
public partial class results : System.Web.UI.Page
{
 
    public int CurrentPage
    {
        get
        {
            // look for current page in ViewState
            object o = this.ViewState["_CurrentPage"];
            if (o == null)
                return 0; // default page index of 0
            else
                return (int)o;
        }
 
        set
        {
            this.ViewState["_CurrentPage"] = value;
        }
    }
 
    protected void Page_Load(object sender, EventArgs e)
    {
        ItemsGet();
    }
 
    private void ItemsGet()
    {
 
        string phrase = Request.QueryString["phrase"];
        DataSet dsResults = DAOCartDB.SPs.SprocCartSelectSearchSimple(phrase).GetDataSet();
 
        // Populate the PagedDataSource control with the DataSet
        PagedDataSource pgResults = new PagedDataSource();
        pgResults.DataSource = dsResults.Tables[0].DefaultView;
 
        // Indicate that the data should be paged
        pgResults.AllowPaging = true;
 
        // Set the number of items you wish to display per page
        pgResults.PageSize = 1;
 
        // Set the PagedDataSource's current page
        pgResults.CurrentPageIndex = CurrentPage;
 
        lblCurrentPage.Text = "Page: " + (CurrentPage + 1).ToString() + " of " + pgResults.PageCount.ToString();
 
        // Disable Prev or Next buttons if necessary
        cmdPrev.Enabled = !pgResults.IsFirstPage;
        cmdNext.Enabled = !pgResults.IsLastPage;
 
        repeaterItems.DataSource = pgResults;
        repeaterItems.DataBind();
    }
 
    private void cmdPrev_Click(object sender, System.EventArgs e)
    {
        // Set viewstate variable to the previous page
        CurrentPage -= 1;
 
        // Reload control
        ItemsGet();
    }
 
    private void cmdNext_Click(object sender, System.EventArgs e)
    {
        // Set viewstate variable to the next page
        CurrentPage += 1;
 
        // Reload control
        ItemsGet();
    }    
}

Open in new window

LVL 1
rito1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

stu28buCommented:
I see two possibilities:

1. There are no onClick events specified on the paging buttons.  Yes you defined the functions, but it doesn't look like you told the buttons to fire those functions.  If you look at the <asp:Buttons> in your sample they have an onClick setting pointing to the functions.
2. Is there a <form runat="server"> that is wrapping things?  You entire ASPX isn't posted so not sure if that is an issue or not.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rito1Author Commented:
Hi stu28bu,

I totally missed the onClick hook!... this was the problem.

Many tanks,

Rit
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.