FormView.AllowPaging Property
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Gets or sets a value indicating whether the paging feature is enabled.
public:
virtual property bool AllowPaging { bool get(); void set(bool value); };public virtual bool AllowPaging { get; set; }member this.AllowPaging : bool with get, setPublic Overridable Property AllowPaging As BooleanProperty Value
true to enable the paging feature; otherwise, false. The default is false.
Examples
The following example demonstrates how to use the AllowPaging property to enable the paging feature in a FormView control.
<%@ Page language="C#" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>FormView AllowPaging Example</title>
</head>
<body>
<form id="form1" runat="server">
<h3>FormView AllowPaging Example</h3>
<asp:formview id="EmployeeFormView"
datasourceid="EmployeeSource"
allowpaging="true"
datakeynames="EmployeeID"
runat="server">
<pagersettings mode="Numeric"
position="Bottom"/>
<pagerstyle backcolor="LightBlue"
horizontalalign="Center"/>
<itemtemplate>
<table>
<tr>
<td>
<asp:image id="EmployeeImage"
imageurl='<%# Eval("PhotoPath") %>'
alternatetext='<%# Eval("LastName") %>'
runat="server"/>
</td>
<td>
<h3><%# Eval("FirstName") %> <%# Eval("LastName") %></h3>
<%# Eval("Title") %>
</td>
</tr>
</table>
</itemtemplate>
</asp:formview>
<!-- This example uses Microsoft SQL Server and connects -->
<!-- to the Northwind sample database. Use an ASP.NET -->
<!-- expression to retrieve the connection string value -->
<!-- from the Web.config file. -->
<asp:sqldatasource id="EmployeeSource"
selectcommand="Select [EmployeeID], [LastName], [FirstName], [Title], [PhotoPath] From [Employees]"
connectionstring="<%$ ConnectionStrings:NorthWindConnectionString%>"
runat="server"/>
</form>
</body>
</html>
<%@ Page language="VB" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>FormView AllowPaging Example</title>
</head>
<body>
<form id="form1" runat="server">
<h3>FormView AllowPaging Example</h3>
<asp:formview id="EmployeeFormView"
datasourceid="EmployeeSource"
allowpaging="true"
datakeynames="EmployeeID"
runat="server">
<pagersettings mode="Numeric"
position="Bottom"/>
<pagerstyle backcolor="LightBlue"
horizontalalign="Center"/>
<itemtemplate>
<table>
<tr>
<td>
<asp:image id="EmployeeImage"
imageurl='<%# Eval("PhotoPath") %>'
alternatetext='<%# Eval("LastName") %>'
runat="server"/>
</td>
<td>
<h3><%# Eval("FirstName") %> <%# Eval("LastName") %></h3>
<%# Eval("Title") %>
</td>
</tr>
</table>
</itemtemplate>
</asp:formview>
<!-- This example uses Microsoft SQL Server and connects -->
<!-- to the Northwind sample database. Use an ASP.NET -->
<!-- expression to retrieve the connection string value -->
<!-- from the Web.config file. -->
<asp:sqldatasource id="EmployeeSource"
selectcommand="Select [EmployeeID], [LastName], [FirstName], [Title], [PhotoPath] From [Employees]"
connectionstring="<%$ ConnectionStrings:NorthWindConnectionString%>"
runat="server"/>
</form>
</body>
</html>
Remarks
The FormView control has built-in paging capabilities, which allow a user to navigate to a different record in the data source. The paging feature can be used with any data source object that supports the System.Collections.ICollection interface or a data source that supports paging capability.
To enable the paging feature, set the AllowPaging property to true. You can determine the total number of items in the underlying data source by using the PageCount property. To determine the index of the currently displayed item, use the PageIndex property.
When paging is enabled, an additional row called the pager row is automatically displayed in the FormView control. The pager row contains the page navigation controls and can be displayed at the top, bottom, or both the top and bottom of the control. The pager row has four built-in pager display modes. The following table describes the four modes.
| Mode | Description |
|---|---|
PagerButton.NextPrevious |
A set of pagination controls consisting of previous and next buttons. |
PagerButton.NextPreviousFirstLast |
A set of pagination controls consisting of previous, next, first, and last buttons. |
PagerButton.Numeric |
A set of pagination controls consisting of numbered link buttons to access pages directly. This is the default mode. |
PagerButton.NumericFirstLast |
A set of pagination controls consisting of numbered and first and last link buttons. |
Note
The FormView control automatically hides the pager row when the data source contains fewer than two records.
You can control the settings of the pager row (such as the pager display mode, the number of page links to display at a time, and the pager control's text label) by using the PagerSettings property. To control the appearance of the pager row (including its background color and font color), use the PagerStyle property. The FormView control also allows you to define a custom template for the pager row. For more information on creating a custom pager row template, see PagerTemplate.
The FormView control provides several events that you can use to perform a custom action when paging occurs. The following table lists the available events.
| Event | Description |
|---|---|
| PageIndexChanged | Occurs when one of the pager buttons is clicked, but after the FormView control handles the paging operation. This event is commonly used when you need to perform a task after the user navigates to a different record in the control. |
| PageIndexChanging | Occurs when one of the pager buttons is clicked, but before the FormView control handles the paging operation. This event is often used to cancel the paging operation. |
Note
These events are not raised when you change the PageIndex property programmatically.
