Re: Opening table - query running?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Just how do you think the recordset is produced if Access doesn't run a
query? Relational databases are NOT flat files. You do not read them
directly. The database engine reads the tables and it does this by creating
and running a query. Rather than arguing with me, prove it to yourself -
use the Database profiler to see what is sent to the server. I'm not sure
how to prove this with Jet tables but perhaps YOU can come up with a way to
disprove it.

"Steve" <sorry@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:v_41i.9026$Ut6.1115@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
<<Opening a table in data*** view always runs a query.>>

Not if the recordsource is a table!

PC Data***
Providing Customers A Resource For Help With Access, Excel And Word
Applications
resource@xxxxxxxxxxxxxxx



"Pat Hartman (MVP)" <please no email@xxxxxxx> wrote in message
news:%235vt3VAlHHA.4848@xxxxxxxxxxxxxxxxxxxxxxx
Opening a table in data*** view always runs a query. That is how data
is retrieved from a relational database. Usually the data is returned in
primary key sequence. Try removing the order by value and see if that
speeds up the opening of the table/query. It should. Access will display
results as soon as it has a full screen of data. However, in the
background, Access will keep fetching rows until all 2,000,000 have been
brought to your workstation. That is why it is poor practice to just
open a recordset that returns the entire table. Use a query that
returns only the rows you want.

"patti" <patti@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:18FE3BC5-CECB-4A0B-939D-8CAE40BE5932@xxxxxxxxxxxxxxxx
When opening a table to view, i notice in the status bar(?- i think
that's
what it's called) says something about running a query.

How do i determine what is going on behind the scenes when this table
opens?
In design view, the table's property *** shows "order by" field filled
in
with one of the fields; is that triggering the message about the query?

It is a very large table of almost 2 million rows and maybe 15 columns.
it
takes a long time to open. is this related to the order by or mysterious
query?

thank you very much for any help.

patti






.

Quantcast