DLookup Usage

[xeb]

Hi:

I have a report that is already based on two queries that needs to display about 25 values (times of the day, activities, etc.) from a table different from the ones tied into the queries. "DLookup" works great, but I was wondering if using 25 instances of it in one report is too many.

Thanks,

xeb

 

[Blorf]

Too many is relative to performance.

If you have only 30 or so rows, with 25 look ups, it not a deal.

I once had do do about 80, on a report with 500 rows. It took several minutes to run.

When it began taking too long, I went to a different strategy, but only then. If you anticipate lots of records in the future, I would suggest finding an alternative. Further, if it will always be only 20 or so records, I would leave it.

ChaZ

Ascii dumb question, get a dumb Ansi

 

[xeb]

Hi:

Thanks for answering.

When you say rows do you mean rows in the table?

The table that my "DLookup" gets its values from has 28 fields with just one value in each field. I don't think there will ever be more than one value in each field, but certainly no more than three.

Thanks,

xeb

 

[Blorf]

I mean rows on your report.

If each row has 28 lookups, and there are 10 rows, no big deal, but if there are 1000, each needing 28, then thats 2800 lookups. Can start to take some time.

ChaZ

Ascii dumb question, get a dumb Ansi

 

[xeb]

Hi:

Thanks for answering.

Just to clarify, my report has 28 "DLookup" expressions in it, each of which delivers one value per field (the only value in the field) to the report. Is that okay?

Thanks,

xeb