to use a recordset? Or maybe a better question is what is preventing you from using a recordset?<BR><BR>If you are talking about accessing your data from an ASP page, then the getrows method is really your best bet here.
the page is pretty DB intensive, and I don't wanna be opening and closing lots of recordsets.<BR><BR>what I'd actually like to do, is have a stored procedure grab all the records from 2 tables according to a certain criteria and pass these 2 sets back to the page as arrays so I can perform some processing on them.<BR>
from stored procedure then you most likely are going to be returning a resultset(i.e. - selecting records) in your procedure. You need to use a recordset here even if it is only for a moment and you use getrows then close the recordset.<BR><BR>Think about it for a sec. Even if you use the command object, you still are going to be creating a recordset when you execute the command object.<BR><BR>Its good that you are thinking about performance, however you really don't have a choice here ; )<BR><BR>Good luck<BR>Pete