>>We ran into the same problem. What we did was to just do a SQL in the order we wanted things in, and then COPY the next n records into an array, and then append the array into a cursor. For a million record table it ran about a million times faster. :) Just make sure you're initial select is a "filtered view" like SELECT * FROM origtable INTO temp ORDER BY OptimizedFieldInTag INTO CURSOR temp.
>
>That's what I was afraid of.
Thanks for the reply, Fred.
It's not nearly as bad as it sounds. And since our SELECTS are buried in a SQL object, the object handles what to do when TOP is used.
