>>This is cheating a little, but you could dump the array into a cursor, using SQL with macros & ORDER BY as needed, then dump results back into array. No one would be the wiser, right? :)
>
>I considered switching from an Array to a cursor.. but, I want to avoid the IO bottle neck for this. The little bit of code will be used in our payroll engine which we claims processes faster than most on the market. Handling a small array in memory should blow cursor speed away.

I don't know about that, cursors/SQL can be extremely fast if they're small and non-complex...so fast that the difference with an array may well be negligible...I don't use arrays much anymore since I've found cursors so quick and more flexible...