Question about query design

  • Thread starter Thread starter W. Guy Delaney
  • Start date Start date
W

W. Guy Delaney

I find myself confused as to when to create a new query and when to use an
existing query. Is it better to design a generic query that returns many
fields but can be used for a number of forms and reports, or is it better to
design more queries that return fewer fields that perhaps are used by only
one form or report.

I guess I just want some guidelines and philosophy on query design--big
queries that have multiple use, resulting in fewer queries in your database;
or small queries that have limited use, resulting in more queries in your
database.
 
JOPO (just one person's opinion)...

I have both in my systems. Sometimes I have a particularly complex set of
joins that returns a dataset from which I need to use only a piece in one
situation, a different set of elements in a second, and so on. Other times
(in the same system!), I only need a few data elements, tightly restricted
by criteria, and so create a very narrow, pointed query.

For me (and I suspect others) it comes down to performance ... if the
approach I start out with is a slug, I spend more time tuning until
performance is acceptable. If performance is critical, I spend even more
time...

Good luck

Jeff Boyce
<Access MVP>
 
I have many queries in my database, each to answer a
specific need or question. Sometimes I even will create,
run print and delete a query without ever saving or naming
it - especially if it is a "one time use" issue.
 
Back
Top