Jim – in case you don't know what Glenn is referring to, look-up fields are a way to view a field other than the foreign key within a table. For instance if you have an Orders table with a CustomerID, you can set that field to be a lookup field that shows the customer name rather than the key. It's really bad practice because the developer has to juggle stuff in forms and reports where they might need the REAL value of the field and not a built-in combo box.
That'll do IT http://thatlldoit.com
My Nothing-to-do-with-Access blog
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: "Bill Mosca" <firstname.lastname@example.org>
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (3)|