Jack, I think your expectations are a bit off. Let me try to explain why I think that...
The reason the entire data set is sorted (and not just the chunk the user is currently viewing) is to prevent user confusion. Let's say that you have the table sorted by 'Request ID' by default and there are 1000's of records in the query. The user is on the third chunk of 100 records (that is 'Request ID' = [200 through 299]). Now the user clicks on the column "Customer Name". If only the third chuck is sorted, then the user would likely not see any of the "Customer Names" that start with "A". Or worst yet they see a few "Customer Name" values that start with "A" and a few that start with "B" and "C", but they do not see all of the "A", "B" or "C" "Customer Names" that are really part of the full data set. So the user might be tempted to be looking for "Customer Name" = "Backline, Bob" and not see it in the set of "B%" records in the third chunk of records and *assume* that there is a missing record somewhere. :) If the sort worked the way you "want it" to work then the user would need to page though all of the chunks to find "Backline, Bob"s record(s) that could be on any or all of the pages (due to the original chunk and sort by 'Request ID') for the chunks that would then later be sorted on the client by "Customer Name". HTH. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 5/23/07, Jack Samson <[EMAIL PROTECTED]> wrote:
All, Does anyone know if you can control the chunk on a table field? If I chunk by 100 and am at chunk 400 and click on the column to sort, it refreshes the entire list and brings me back to the first chunk. Any way to control this? We are using version 6.03. Thanks, Jackson
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
