Discussion: using combobox & listbox lookups in table field design

Ola all. In responding to a recent post requesting help with a search
issue, I recommended using a combo box lookup in the table design.
"paii, Ron" (no relation) posted this reply:

" There are many posts in this group explaining the pitfalls of using
the
lookup feature in tables. Best practice appears to be, keep the
lookup in
the forms using combo box or list box."

I will grant that, in a theoretical world, best practice is to handle
data only on the data side, and leave the interface on the GUI side.
Point taken.

However, I think that its possible to distinguish between 'pitfalls'
and 'annoyances', and also necessary to distinguish between database
theory and production application design.

In my experience the only major annoyance with table field lookups is
that it's often confusing for users because a standard search for
'known' displayed values will return no hits. That annoyance is way
offset by the fact that by properly structuring table field lookups,
those lookup features are automatically propagated thru to the form -
in the form designer you can drag and drop the fully designed lookup
control on any number of forms. 'Design once - instance many'

I'm wondering what you all think about this - are there other
'pitfalls' that I'm not aware of? Does the convenience of a design
shortcut offset the stigmata incurred by breaking the taboo of pure
relational design? Any strong opinions? Fill me in...

Ron, King of Chi

.