Queries and Report Optimization Question

  • Thread starter Thread starter cefrancke
  • Start date Start date
C

cefrancke

Which is typically faster or preferred...

Let the query do the calculated fields or the report?

Join tables and let the query lookup the fields or only include the
lookup table ID's (foreign keys in master table) and let the report
lookup the values in combo boxes?


TIA
 
I don't believe there's much of a difference between doing the calculations
in the query or in the report. I typically do them in the query, because I
can then use the query elsewhere if I need to, and be sure of the same
calculations.

I definitely wouldn't put combo boxes on a report: that's pointless, since
combo boxes are meant for interaction, and you can't interact on a report.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DB Optimization Questions on reducing Table/Query count 2
Using a Parameter Query in a Report? 2
Form w/ combo box from query based on lookup field not alphabetizi 5
Lookup query allows me to retrieve up to two rows. 1
Problem with errror 3341 6
how do you show all fields from linked data? only shows first one 1
Generic Query? 1
Table Lookup Field - options relative to record 1

Back
Top