>You should only ever work with a subset of the data. For example, the user enters the supplier id. The record for that one supplier is pulled back. Or the user can request to get all suppliers in New York. This gets you a subset of data. The previous/next buttons we're all used to then work on that set of data, not the entire table. If you need to supply a search by product description, the user can enter the first part of description, then pull back the records that match what the user entered.

So this is what I was afraid for : not only the developer has to change habits : also the user will have to ...
I'm willing to believe that this doesn't have to result in decreasing (from the users point of view) performance/userfriendliness/etc ... (though discussable) but I'm wondering if users used to one system easily will accept a more tight way of working ...