Serious performance problems with ODBC/Access/Win NT 4.0.

When scrolling past the last record in a CRecordSet for a IsEOF() check
the ODBC driver uses 1-2 minutes to return. It starts some havely disk
operations. Why? What is the database/recordset doing?
The table in the database is fairly big (50000 records), but the
recordset is filtered down to ca. 10 records when opened (no sorting).

ex. code:

while (!r.IsEOF())
 r.MoveNext();

Anyone familiar with this problem?

- Haarek Ryeng