I am using ADO to access data from a SQL Server 6.5 source. If I set MaxRecords to <= 1000 I get good performance. If I go higher than that, I get timeout errors.

This brings up two questions.

1) Is there a practical, from a performance standpoint, limit to the number of records ADO is going to want to return at a time. If so, any body got any suggestions on a "pageable" recordset that I can move through blocks of records seamlessly for the user?

2) If this is in fact a limitation of ADO, and not my understanding, how can this be touted as the thing in data access ???

I deal in terms of 500,000 - 1,000,000 records.

My thanks for everyone's thoughts.

Regards,

Jason