You have a couple of options --
You could store all the values in a multidimensional client side array -- using the method that is outlined in the FAQ, but depending on how much data was in the recordset, that could be one big array --
Otherwise, you could store the recordset in a session variable (although this isn't a practice that's smiled upon because it eats up server resources, and isn't good for high traffic sites)...
I guess of the two, probably the first is the best idea, but if the recordset is huge, it could make lesser machines creak and rattle... with all the data in memory.
It's fairly well agreed upon that multiple trips to the server for data isn't necessarily a bad thing, that is, of course, if your other options provide even worse performance than this option...