That really helps me out too, Ed. Thanks for the info.
I haven't checked this yet, but I'm assuming if you leave the
vertical scroll on, then you should be able to have large (e.g. 50,
100) page sizes without some data becoming inaccessible, so I would
imagine most important property to set is rowCount=pageSize.
I was thinking one step above where I should have to make
full use of the built in paging; I was looking for an answer at the
DataService level rather than at the actual point of delivery for
the data. It makes perfect sense to do it that way, and treat
rowCount as analogous to pageSize, and the value for
scrollToIndex(desiredPage*pageSize) as analogous to currentPage.
In fact, it should be pretty trivial to extend DataGrid in a
new class called PagedDataGrid or similar which exposes various
properties and methods more logical for the task at hand, such as
nextPage, previousPage, setPage, setPageSize, bindable properties
for hasNextPage, hasPreviousPage, currentPage, pageCount, etc.