I'm not much into web solutions; you might want to report this question as new
in the appropriate category and see if Rick or one of our more web-conversant propellerheads picks up on it.

>But as an aside, one of the future specs of this project is display data from an ADO recordset within a web page, via ASP. I tested this out and the ADOR returns 150 records. The client wants to see 120 records per page with buttons to go to the next/previous pages. Since the recordset is disconnected does the above solution apply? If so, are there siginificant performance hits? And if not, any ideas what I might get this done?