J
JoMcGuire
Below is a quote from a post from several years ago. My question is,
does it significantly affect the processing speed of your program when
you have several levels of queries.
I'm working with a programmer who creates two queries for every table -
whether he needs them or not - ( one with everything in the table ..
one with only "Active" designations). When I was helping him build a
cross reference report, I created two queries to get my cross
reference, but my queries queried his pre-fab queries instead of tables
and we got about 6 levels deep before it was all over.
It seems to me that we are asking Access to do more steps than
neccessary. Am I wrong. Will it affect the speed at all or such a
minimal amount that it won't matter?
Any opinions ?
Thanks.._
____________________________________________________________________
"BB,
You can theoretically go 50 levels deep. (My head would explode first,
but
apparently Access can handle it <g>). There is, however, a limit of 32
tables, and you're probably more likely to hit that first....
HTH
does it significantly affect the processing speed of your program when
you have several levels of queries.
I'm working with a programmer who creates two queries for every table -
whether he needs them or not - ( one with everything in the table ..
one with only "Active" designations). When I was helping him build a
cross reference report, I created two queries to get my cross
reference, but my queries queried his pre-fab queries instead of tables
and we got about 6 levels deep before it was all over.
It seems to me that we are asking Access to do more steps than
neccessary. Am I wrong. Will it affect the speed at all or such a
minimal amount that it won't matter?
Any opinions ?
Thanks.._
____________________________________________________________________
"BB,
You can theoretically go 50 levels deep. (My head would explode first,
but
apparently Access can handle it <g>). There is, however, a limit of 32
tables, and you're probably more likely to hit that first....
HTH