|
|
Posted by Neil on 10/16/55 11:29
> Well, there may be lot's of reasons, but I didn't see
> anything in your description that ruled out a first time
> through delay. The first time you access the recordset may
> require a bunch of connection activities to take place.
Yes, I should have mentioned that I did these tests repeatedly to rule that
out: go to record 100 (very slow); then manually move back to the first
record; then go to record 100 (still very slow); then back to the first
record; then go to record 50,000 (very fast); then back to the first record;
then go to record 100 (very slow); etc.
I should have noted that. Sorry.
> Another likely cause is that the first search fills the
> memory cache so subsequent searches don't have to go back to
> the server as often as the it did the first time. To
> verify/refute this hypothesis, reboot your system between
> each timing test.
How would that explain why it's very fast when going to a record at the end
of the set?
>
> Note that you can often avoid all this kind of stuff by
> filtering the form's dataset instead of loading all the
> records and then searching for the one you want, especially
> if the filter field is indexed.
Yes, indeed. This is something the client wants, though, as they like being
able to switch back and forth between form view and datasheet view.
Otherwise, yes, that would be a better way to go.
Thanks,
N
>
> --
> Marsh
> MVP [MS Access]
Navigation:
[Reply to this message]
|