Is there some type of "PRE-FETCH LIKE" Function ?

[kev100 via AccessMonster.com]

I've got a query that is based on a massive SQL table (use an ODBC link to
the SQL table).

The query works fine. However....it seems unnecessarily sluggish when
scrolling down the list of returned records.

While the average query may return a list of around 100-400 records......when
I begin to scroll down through them.......there are long pauses before below
entries will appear....like the query is processing on an as-needed basis.

But...since it already indicates how many records were returned (usually less
than 400) at the bottom of the query window...you'd think any needed
processing had already occurred.

Is there any type of PRE-FETCH function......something that will do any
needed processing before the results are displayed?

Waiting a little longer for the query to fully process would be fine...if it
allowed the returns to be scrolled through more easily.

Any advice appreciated.
Thanks

 

[Pat Hartman \(MVP\)]

Are there any functions in the query that could be causing recalculation as
the recordset scrolls?

 

[kev100 via AccessMonster.com]

Are there any functions in the query that could be causing recalculation as
the recordset scrolls?

Not that I can see.

All the query does is simply display the contents of the fields based on 2
parameter queries

On Employee ID is the criteria [Enter Employee ID:]

And on Date is the criteria [Enter Date:]

Other than that...all querying occurs on the SQL side (the SQL table linked
to is actually a View comprised of 3 joined tables)

What seems odd is that as soon as the initial results appear (the first page
full)...the correct number of total returned records is accurately displayed
at the bottom......so....it seems like any processing would have already
occured.

ALSO...the pauses seem to occur when scrolling down 10-11 more records....
pressing the down-arrow key that 11-12th time seems to be where the pause
consistently occurs.

Thanks very much.

I've got a query that is based on a massive SQL table (use an ODBC link to
the SQL table).

[quoted text clipped - 22 lines]

Any advice appreciated.
Thanks