|
>> but if the DB you are reading from, is big a customer file is often BIG), and you just need a handful of those records, I would still position in the DB and reload the subfile... If that was indeed the requirement I'd probably use SQL. Also of course the limit on a subfile is 9,999 so you can't hold that many records in memory anyway. If because of the size of the file (and subsequent result set) we are into displaying a page at a time anyway, then a memory sort is problematic in other ways. I think it really depends more on _why_ the user wants the subfile sorted. If they are looking at a set of records and want to see the same data in a different way, I'd load the subfile into memory and sort it. If on the other hand they are (say) trying to find a specific record and using different sequences to help locate it then I would agree with you. However, in this case I'd have probably presented them with a "search by ..." type screen rather than having shown them a subfile and then have them request a sort. Jon Paris Partner400 www.Partner400.com www.RPGWorld.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.