I’m glad you followed your gut instinct and stayed with your design. It would be interesting to know your advisor’s reasoning for avoiding lookup tables and what he suggests as an alternative.
You don't need to define lookup fields in tables in order to use combo boxes on forms.
I was referring to my own combo boxes with the tables as the record source and it was clear that that meant too many tables to have in the design, I suppose.
But I do not know of any other way to get a select list of choices into a combo box without using lookup tables. So I stayed with my design and ignore his comments.
Was the developer perhaps referring to lookup fields, rather than lookup tables? Most developers agree that lookup fields are poor design.
A developer recently told me that using lookup tables is bad design. I argued that it is not possible to have drop downs on a form without having some data associated with the dropdown so users do not make spelling errors for one. it gives users limited choices, so they do not have the wildest things typed.
I began thinking how would anyone have combo boxes without lookup tables? What do other developers do especially SQL backend users?
Posted by: "Glenn Lloyd" <firstname.lastname@example.org>
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (6)|