|
Peter we have samples on IGNITe400 for Net.Data including the previous/next processing quite a few more than the IBM site. Sounds like you are not incrementing your counter for the next start position on your search. Check the variables being passed in for the start point, look at your generated HTML. http://www.ignite400.org/html/iseries%20netdata.htm Thanks Bleddyn http://www.ignite400.org - iSeries eBusiness User Group I'm trying to implement PREVIOUS|NEXT processing for search results when particular selection criteria return a large result set. I used the example in the "Net.Data Reference" manual under START_ROW_NUM; pretty much the only difference is the SELECT (I use a WHERE and an ORDER BY) and how I format the results. The code for handling the PREVIOUS|NEXT processing was copied/pasted. The results are limited to RPT_MAX_ROWS as expected, and the NEXT href is formed correctly, however, when clicked, the result is not the next set of records, but the 1st set. Any ideas what I'm doing wrong? I'm on V4R5 using the classic HTTP server. I can post code if that would help find the problem.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.