ClassicPaging; None; and VirtualLoad represents how the data should be retrieved in WebGrid.

• ClassicPaging is defined by a set of navigation controls (such as First, Previous, Next, and Last) to control the active page. In ClassicPaging, the total number of visible rows is a constant number.

  To enable classic paging, simply set PagingMode to ClassicPaging. You can customize the number of visible rows in one page by setting the PagingSize property. By default, the PagingStyleUI is set to FirstPrevNextLast style, which will display a set of paging commands in the status bar.

• None means no paging. All rows will be loaded on first page load.

• VirtualLoad will load only a number of rows that specified in VirtualPageSize property. To enable VirtualLoad, simply open the WebGrid.NET Designer and set the PagingMode to VirtualLoad. The default value of VirtualPageSize is 50 which you can customize to fit your application's needs.

You can choose which PagingMode method that will be use on your WebGrid. I’d like to suggest you to set the VirtualPageSize or PagingSize property based on the PagingMode method. For example: if ClassicPaging is used, then you can customize the number of visible rows in one page by setting the PagingSize property; or if VirtualLoad is used, then you can customize the VirtualPageSize property to fit your application’s need.

This suggestion can help make your code easier to read, although declaring PagingSize and VirtualPageSize altogether will not cause any problems.

In order to set the load on for the child rows, please kindly check the LoadonDemandChildRetrieval.aspx sample file in WebGridSamples project or the live sample at http://live.intersoftpt.com/cs/WebGrid/LoadonDemandChildRetrieval.aspx?noframe=1.

The sample uses ISDataSource control to perform codeless load on demand data retrieval. Child rows data of its parent row will not be rendered to client on each loaded table. The child rows of a table will be retrieved transparently when user click on + sign to expand the child rows. This results in efficient information delivery by displaying necessary information and load more information transparently when needed, all without leaving the current state of the working page.

I’m afraid that it is not possible to have paging for child rows. The rules of paging will be implemented on the root table level. Suppose the parent has 100 child items, these items will be loaded once when user expands the parent.

Hope this helps.