Skip to main content
Inspiring
July 1, 2006
Answered

Paging with ASP

  • July 1, 2006
  • 1 reply
  • 917 views
HI. I have a search and results page that work fine with regard to filtering via SQL statement. I can view all recordsets using the filters as applied in the search page. The issue is when I try to limit the number of recordsets viewed to say 5, the results of the 'Next' button as applied via the Recordset Navigation Menu returns a results page but it contains no data - it is simply a page without the table where my next records should be. I am guessing that the paging procedure is not working - dropping the recordsets held in limbo. Where would I start to look for the cause. I have looked at Stored Procedures and this seems to be not the area I am looking for. Any pointers please.
Paul
This topic has been closed for replies.
Correct answer FissDesign
Thank you. Partial success. The paging works now but when the next button is clicked the results page moves along by one record instead of the next 5 records from the same recordest. How do I get the results page to jump 5 at a time?

Paul

Update. Removed the paging code and put back in again - using images this time. It worked. Thank you everyone.

1 reply

Inspiring
July 1, 2006
Do you really mean "number of recordsets"? Or do you mean the number of
records in THE recordset? I'm assuming it's the latter .. which is what you
do with paging. Did you select the word NEXT to apply the "next" paging
behavior and then specify the correct recordset (or probably the only
recordset)?


--
Nancy Gill
Adobe Community Expert
BLOG: http://www.dmxwishes.com/blog.asp
Author: Dreamweaver 8 e-book for the DMX Zone
Co-Author: Dreamweaver MX: Instant Troubleshooter (August, 2003)
Technical Editor: DMX 2004: The Complete Reference, DMX 2004: A Beginner's
Guide, Mastering Macromedia Contribute
Technical Reviewer: Dynamic Dreamweaver MX/DMX: Advanced PHP Web Development


"FissDesign" <webforumsuser@macromedia.com> wrote in message
news:e85uou$4r8$1@forums.macromedia.com...
> HI. I have a search and results page that work fine with regard to
> filtering
> via SQL statement. I can view all recordsets using the filters as applied
> in
> the search page. The issue is when I try to limit the number of recordsets
> viewed to say 5, the results of the 'Next' button as applied via the
> Recordset
> Navigation Menu returns a results page but it contains no data - it is
> simply a
> page without the table where my next records should be. I am guessing that
> the
> paging procedure is not working - dropping the recordsets held in limbo.
> Where
> would I start to look for the cause. I have looked at Stored Procedures
> and
> this seems to be not the area I am looking for. Any pointers please.
> Paul
>


Inspiring
July 1, 2006
Thank you for replying. I have just created a test search and results page and created an SQL for 2 pull down menus with options to select. The SQL works fine. I can select my options and the results page reflect my choices. As soon as I put a paging attribute onto the page with a repeat region the results page returns to intial records up to the limit of the repeat region value. As I hit next, expecting the next records (and I know they are there) the results page returns nothing. It seems I cannot get the next 'x' number of records to display. If I turn of the Repeat Region and allow all records to display they all fall back in. Very curious.
Any clues please. All seemed to be going smoothly at one point.