Look up at table level vrs. row source

[sblanche]

I have a DB that I designed 10 years ago. We need to redesign. We have about 10 fields that have some simple look up values. An example would be the type of case. They are either C, L, A, or M. I may at one point add more types, but for now it's the 4. Instead of putting those picks at the table level on the LOOKUP tab, I put them on the forms in the "row source". I'm trying to remember my logic on why I did not put at the table level since if I add another type of case, I will have to go to each form that has the "CaseType" and add it there instead of just one time at the Table level. Any suggestions on why one place is better then the other would be most helpful Using Access 2010. thank you very much--

 

[dhookom]

I almost always use a table for combo and list boxes and never use "Lookup" fields in table designs The Evils of Lookup Fields in Tables.

I assume the list will change. It would be frustrating to have to go back and find all of the value lists.

Duane
Hook'D on Access
MS Access MVP

 

[sblanche]

Thank you so very much for the link to "the evils of Lookup Fields in TAbles". I have people pushing me to move the "pick lists" from the Form "row source" to the table "lookup" tab. I knew there must have been a reason I designed it that way in the first place but after 10 years I could not remember why. Thanks again--

 

[dhookom]

One of the issues is people like to edit records in table datasheet views. IMO, users should never be presented with a table. All interaction should be through forms where you can create/use combo boxes.

Duane
Hook'D on Access
MS Access MVP