"table level dropdown lookups": why not?

[Frank H]

I've seen several posts stating not to use them.
What are the reasons not to use them?

 

[Gina Whipp]

Frank,

http://www.mvps.org/access/lookupfields.htm

In the future, you'll want to put the whole question the big white space as
some newsreaders crop the subject line. And without your subject line the
rest of the statement is useless.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[John W. Vinson]

I've seen several posts stating not to use them.
What are the reasons not to use them?

http://www.mvps.org/access/lookupfields.htm

Mainly, they are a huge source of confusion. The table APPEARS to contain a
looked-up value. It doesn't; it actually contains a hidden numeric foreign key
value. This tricks users into trying to (say) sort by the looked-up name, or
put a criterion on it that fails, because the field does NOT contain "Acme
Tool Co." (but in fact contains 312), so it doesn't sort by Acme nor does it
search by LIKE "*Tool*".

The lookup field has two benefits: it makes it easier to use table datasheets
for interacting with data (which is in fact a detriment as it is much better
to use Forms for interacting with data); and it makes it one or two
mouseclicks easier to put combo boxes on Forms. In my years on these forums,
I've seen FAR more detriments than these two minor benefits.