One more problem - sorry !
Using MS Visual Basic 6.0, the application I'm working on accesses a 21 Mb .mdb, with @250,000 records, file on a file server across a network. The result of a search normally returns about a dozen records to the recordset.
Opening the recordset with a search usually takes less than 10 seconds, and looping through the majority of records in the recordset, to fill a list box, takes a fraction of a second.
My problem is that retrieving the very last record in the recordset takes around 25 seconds, making the total about 25 seconds (too long for me!). The loop is of the form -
While not recordset.eof
.....
recordset.MoveNext
......
Wend.
When the recordset tries to MoveNext and hits the EOF, execution takes a long time (as observed by tracing though).
I've tried finding the matching number of records in the set by query, and reading an ADO static recordset's RecordCount property, but both of these reduce the total time by no more than 10 seconds.
Is there any way to avoid this EOF trap in using a recordset loop ?
Thanks in advance for your help.
Peter Jenkin
Using MS Visual Basic 6.0, the application I'm working on accesses a 21 Mb .mdb, with @250,000 records, file on a file server across a network. The result of a search normally returns about a dozen records to the recordset.
Opening the recordset with a search usually takes less than 10 seconds, and looping through the majority of records in the recordset, to fill a list box, takes a fraction of a second.
My problem is that retrieving the very last record in the recordset takes around 25 seconds, making the total about 25 seconds (too long for me!). The loop is of the form -
While not recordset.eof
.....
recordset.MoveNext
......
Wend.
When the recordset tries to MoveNext and hits the EOF, execution takes a long time (as observed by tracing though).
I've tried finding the matching number of records in the set by query, and reading an ADO static recordset's RecordCount property, but both of these reduce the total time by no more than 10 seconds.
Is there any way to avoid this EOF trap in using a recordset loop ?
Thanks in advance for your help.
Peter Jenkin