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.
Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT http://thatlldoit.com
My Nothing-to-do-with-Access blog
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Saturday, August 20, 2016 12:06 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Look up tables
Jim,
Was the developer perhaps referring to lookup fields, rather than lookup tables? Most developers agree that lookup fields are poor design.
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Saturday, August 20, 2016 2:10 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Look up tables
Hello all,
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?
Thank You
Jim Wagner
Posted by: "Bill Mosca" <wrmosca@comcast.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar