Steven,

Typically you can get around this by using a where clause and/or a TOP and ORDER clause in your select statement. The logic is basically using a field in the last record displayed to determine the where clause for your 'Next' method. Of course you want to use the field from your first record to query for the 'Previous' method. For this you will have to reverse your ORDER BY for the initial select if you want the TOP to pull the right set of records. Then you can temporarily index on the client to get them in the right order. There are most likely better ways to accomplish this.

It may take you a bit too work through all the logic but the performance benefits will be much greater.

Also, if you need the count to determine the number of pages it's usually faster on large tables to do the query just for the count, then do a seperate query to pull a small number of records.

Greg


>One problem is navigation on my display form. If I don't pull the whole set how do I go to the next record or previous record? Although I may have this resolved. I am pulling five records plus/minus in my spt. this seems to take no more time that pulling one record and I have what I need I think.