What I do is I call a dll written in vb that executes the sql and returns a record set the problem is the record set is so large the response time is very slow. I am wondering if anyone else has ran into this and has devloped a way to only return portions of the record set each time.
It's called "pagination". The theory doesn't really change because you've hidden the SQL query inside a custom COM object.<BR><BR>You take your data set, break it apart into managable chunks, and then make your ASP page request it in chunks.<BR><BR>However, I would say that sending a recordset containing several thousand rows to the end-user is meaningless. They won't know what to do with it. In that case, you may be better offering several "pages" to the end user. In that case ASP only cares about a small subset of those thousand records. In that case you should be restricting the dataset returned to ASP based on the pagination. In that case your DLL probably doesn't need to know about all the thousands of rows either...<BR><BR>Read up about pagination - I have a feeling you're approaching this from the wrong direction.<BR><BR>Craig.