SQL question

[Matt Brown]

I fully understand the concepts of SQL and how to query databases but this has sort of been bugging me for a while...

I have a frontend and a backend databases which are linked, When i load up a particular form which has a query attached to it, the query obviously queries the tables and returns the results of the query to the form. No problem there..
My question is when i go through each record, lets say the query found 1000 records, you can see it calculating in the bottom left of my screen, is it querying the tables again and pulling the next record across or does it pull all of the records over in one block on the first query, if so what is it calculating?


[This message has been edited by Matt Brown (edited 02-22-2002).]

 

[Pat Hartman]

Since it is unlikely that anyone would actualy want to scroll through a thousand records, it would be much more efficient to filter the query so that fewer records need to be retrieved. But, to answer the question. Access presents the form as soon as some records are retrieved and continues building the rest of the recordset in the background. When the recordset is fully built, you'll see the final count shown in the lower left of the form as record x of y.

 

[Matt Brown]

Pat,
Thanks for your reply, though i am still unsure, if the recordset has been built what is it calculating when you click lets say the next record button(it starts calculating again) is it pulling the next record out from the record set or is it re-querying the the backend table again which seems does not seem logical if the record set has already been built.?
(The 1000 record qty was just a hyperthetical amount)

Matt

PS I have missed something out here, what has happened to your status????

PPS forget the above PS if you have already read this post, just seen your post "Where am i?


[This message has been edited by Matt Brown (edited 02-26-2002).]

[This message has been edited by Matt Brown (edited 02-26-2002).]

 

[Pat Hartman]

The Jet programmer's guide explains this in some detail. I think there are cases where Access will first build a keys only recordset and then go back for the rest of the columns as necessary.