Unanswered: adding a field from a qry that isnt the reports record source
i have a rpt employees, the record source is qryEmployees, i have another query that has nothing to do with employees and need to add a field from that qry to the employee report. I added a txtbox went to the data tab and added =[Query220]![NetProceeds] but when i go to view the report i get prompted to enter the parameter value for Query220
or failing that why not add the element you want intot he query.. dlookups' can be a real performance hog. if you have only a few dlookups its probably ok..., if you have many the report may well have severe problems.
likewise if you use a lot of aggregate functions in report footers (page, group etc) it may be better for performance reasons to do the aggregation yourself than issue a series of aggregation commands in SQL,
What do you mean by "do the aggregation yourself"?
if you use a lot of sums/totals in footers Ive found it can take a long time to let the report mechanism do the footers itself.. each column requires a separate SQL command... talking to a large data set with lots of groups can make the report very slow.
doing simple aggregation (by summing the totals yourself in the reports on detail event can save a significant amount of time). natch it won't work if you are using complex statistical functions. but it will work for simple arithmetical operators and basic stat functions. If you are using dLookups in reports, especially more than one per row then you will have a real performance hog, occasional use of domain functions is great, but in my books the occasional should be in bold type. Usually you can get to what the domain functions give you via another route and usually more cheaply