DLookUp on a table taboo

[FuzMic]

Hi guys

I was just reading DCrake's 10 commandments and saw the taboo of using LookUp fields; i presume it is has nothing to do with DLookUp which i use extensively to look up a (one) value from a table; is this not ok?

 

[pbaldy]

No, they are different. DLookup() is okay, though if you use it extensively you may be misusing it.

 

[FuzMic]

Pb why do you say I should not be using Dlookup extensively, what is the alternative

Sent from my HTC_PN071 using Tapatalk

 

[pbaldy]

Not knowing how you're using it, I can't offer "the" alternative. They could include recordsets, joins in queries, etc.

 

[The_Doc_Man]

The "implied Lookup" whether as a lookup field or a DLookup in a query involves multiple "hidden" queries and thus incurs tremendous overhead. There are usually a few exceptions to any rule, but in the case of a lookup operation, the most efficient method is USUALLY (and this is emphasized: USUALLY) based on a query that joins the base table to the table that would have been the target of the lookup, joined on the code field in the base table and USUALLY the PK of the lookup table (if that is the field that holds the code.)

Special cases will always be found where the above is not right. Access has entirely too many ways to skin cats <MMEEEOOOOWWW> to say that it is cut-and-dried that method X is always right.

 

[FuzMic]

for the care

Sent from my HTC_PN071 using Tapatalk