Hey, if you are using Java/JSP and/or servlets you can always save your rs object in the session, which would make it remain accross browser transactions...BUT I have never tried it that way...

I also NEVER work with MS Access unless it is on my desktop...it is just not a good choice even for learning...despite what the book might have told you... PostgreSQL or MySQL are free and VERY simple to download and install/setup if you follow the instructions, in the old days they were more difficult, but today they are a breeze... use them...

I have Apache Web Server, Apache Tomcat and PostgreSQL installed on my Windows XP laptop and use them for dev testing and POC (proof of concept) creation all the time...it is a better learning environment, so I suggest you invest 2 hours and set them all up...they can all be done in 2 hours total or less usually...

You should have an "order by" in your SQL to ensure the order is always the same... then use a limit and offset to depending on the DB support, some accept "limit 10, 20" for ten at a time starting from record #20... others use 2 separate keywords "limit 10 offset 20" ... once you know which way works for you DB, you can set limit 1 and offset iNum where "iNum" is the record number to show...

you set input field in the page to have the current value (or next value) and use those to figure out what the offset should be next time around...

i.e.
<code>


<input type="hidden" name="next" value="<%=iNum%>">

</code>

you could extend this then to provide forward and back or even jump capability for your records, but you would be reselecting the record each time, so you must be sure they are properly ordered with the "order by" keywords