have a older ASP 3.0 application that exists. I also have a .Net newer version but it has not been implemented yet and won’t be for a while. I have 2 ASP 3.0 pages that the user types in a Part Number and then 200 records show up and then at the bottom of the page if there are more than 200 records in many cases there is a previous and next link that reloads the page with the next or previous after the first page 200 records. So there are always a max 200 records on the page and then the links. The way I handle the break up of the records is there is a identity column called av_id that the first time in I get the min(av_id) and then 200 records and then the next Top 201 records where av_id > the av_id I pass to the stored proc.

Well this worked fine for a long time until we just noticed that there is an order by on the procs. Well the order by works based on the “current” 200 records on the page but then the next 200 records it starts again with the order by because I am using this identity column to handle it.

The goal is to recreate the data points of these 2 pages very similar just different tables to have the order by happening from the start to finish and not just by the page. I am not sure the best way to handle it. The page runs very fast currently so I need to be able to keep that speed.

I need this completed ASAP and the 2 pages are somewhat detailed. I want to cut down the database calls if possible as well to speed it up even more possibly storing the data in an array or something not sure what way to handle it best. But I think the code and the amount of procs can be limited down.

I would send the pages and a sample database for you to work on. I am hoping to turn this around in about 2-3 days if possible. You must have solid SQL Server and older ASP 3.0 design skills.