Thanks, David, but actually I did understand what you are saying. I know that every database I have used has some way of limiting queries for the purposes of paging through the results. Pagination is logically separate from a set of filtering criteria in that it is an additional criteria on top of the filtering. MySQL does that with the LIMIT clause; Oracle lets you put ROWNUM in the where clause. I see that SQL Server is pretty messy, giving you a "TOP N" or a ROW_NUM() function in the select clause. I've played with these but they don't seem to work in MethodCRM.
The prototypical example usage of this is a paged presentation of data; you start out by saying "give me THE FIRST N records that meet such-and-such criteria", and then I'd display those N records on a page; when the user clicks "next page", I fetch the NEXT N records, etc. You have an example on methodintegration.com site: click Customers, which will take you to a E xisting Customer Contacts List page that lists the first 10 records, with a "Next page" button at the bottom. I want to be able to do something like what you do on the Existing Customer Contacts List page. Or, let's turn this around: how would you do such a page using the API? Maybe there's something I'm missing.
Sorry for being such a pain, but I really need to do something like that and I can't believe it's never come up as a requirement before. Thanks for your support.