Slow Query

[Agent_KGB]

I have a table with good 40K lines of records, and i am trying to build a
querie to analyze the data based on some data...

what's the best way to handle building queries to handle large amount of data?

Should i try to stick with one querie that handles all of the work i need,
or would it be better to have a bunch of subqueries each one handle a little
part of the calculation and then just bring it all together in one MASTER
querie (where SubQs would work with data from tables and Master would pull
data from subqueries only)?

 

[Jeff Boyce]

Can you provide any more explicit explanation, or an example?

40K records is not all that large. If your query is slow, there could be
many reasons why.

For example, is your underlying table indexed? Properly?

Is the data stored in a file on the network, while your query is in a file
on your PC? How fast is the network? How fast is your NIC?

Is your query doing any 'calculations', or using any functions? Which ones?

(this is just a start ... more specific description may lead to more
specific suggestions)

Regards

Jeff Boyce
Microsoft Access MVP

 

[Agent_KGB]

I have a few calculations IIF statements to make it easier to solt data once
i move it to excel

all of the data is on my PC, so network would play a part it in...

when i imported last data file, it had a different structure and all of my
fields went into wrong places, i think that was the problem for my query
taking so long.

thanks for advice

PS: how much do calculations (such as IIF statements) slow down your query?

 

[Jeff Boyce]

There are so many possible factors that about the only way to tell how much
YOUR IIF statements slow down YOUR query is for YOU to test it.

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP