Lookup fields in tables

[lefty2cox]

I read from some posts on a forum (can't seem to find it again for reference) in which it was the opinion of the poster that it is not good practice to have lookup fields, for example a combo box, in tables. The poster stated that the control on a form should lookup the value and then store it in the table. If anyone agrees, I was wondering if they could explain why. I am new to access and am in the planning stages of a database.



The down side to not having the look up value in the table, from what I have observed, appears to be that it requires that the corresponding control on the form needs to be created manually since the wizard will not work for these fields, which also seems preferable to many as I've read.

Thank you,

[RuralGuy]

Perhaps reading this link will be helpful: http://access.mvps.org/access/lookupfields.htm

[rzw0wr]

Lefty,
It is general agreement between MOST developers that lookup Fields are not to be used.
I will use them sometimes. I keep in mind that no other person will likely have to troubleshoot my databases.
Usually what you can do with a lookup field you can do in a form easier once you find out how.
Mostly the main argument with lookup fields is what you are storing in the table and the unneeded relationship made between the 2 tables.

My advise to you would be to learn to make and use combo boxes and forget about lookup fields.
They can be a giant headache and there are easier ways.


Dale

[lefty2cox]

Wow...compelling arguments supporting the position. Say no more and thank you so much.

[RuralGuy]

@Dale: I'm sure you meant to say "Lookup FIELDS" rather than "Lookup TABLES". We use Lookup Tables *all* of the time.

[lefty2cox]

Thanks RuralGuy. I believe that's what Dale meant and is what I assumed.

[rzw0wr]

Yes RuralGuy.
You are correct.
Lookup fields made in tables.


At any rate. Use the with care and best not at all.

Dale

EDIT: thanks RuralGuy. Wording has been changed in my post.