Thanks for your response, Rick. However, if I I was performing a task that
required one or the other, I wouldn't be asking this question. As I said in
the initial post, I have multiple controls coming from different tables
linked by a common field. Maybe I wasn't clear though about how only 1 row
of data from the sub-tables per report is being accessed, but anywhere from
5 to 12 controls (fields) per table is being used per report page. And,
I've got 5 subreports (hitting on 5 separate tables via queries) doing all
this. So, would it be faster to continue using this method, or would it
behoove me to rewrite stuff to do lots of dlookups instead--that's my
dilemma. Or, would even sub-queries be faster?
I'll experiment. But, again, thanks for your response Rick,
ron
"Rick Wannall" <wa*****@notadomain.de> wrote in message
news:MU******************@newssvr11.news.prodigy.c om...
More important to your question is the fact that DLookup and subreports
are
not substitutes for each other. If you have multiple rows of related data
to display, you're going to have to use a subreport.
Example: A customer can have many orders (order headers). An order
header
can have many details (order lines).
If you want to print a customer and then a list of his orders, you must
use
a subreport. There is no way with dlookup() to generate the multiple
linesyou would need to represent each of the lower level (order header)
records.
If this is similar to your task, the relative speed of dlookup and
subreports is not relevant.