If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
"Evils of Lookup FIelds"?
SO I've read a little thing that warns against using the
LOOKUP feature when designing tables. Apparently its not good to assign values to a field based on values in another table; better to just join the tables in a query and get your values that way. But what about using the VALUE LIST lookup option when designing a table? This does not reference another table, but you just type in the list of values from which you want the user to select. For example, I might want to limit data for a Status field to "Approved," "Pending." and "Denied." SO rather than creating a separate table for these 3 entries, I just type them in to the table design, via the LOOKUP feature. Any harm in that? (Thanks!) |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Troubleshooting Lookup Fields | blaqkikapoo | Database Design | 2 | August 9th, 2004 10:37 PM |
Lookup fields on label report | Howard | Setting Up & Running Reports | 1 | June 3rd, 2004 02:43 AM |
Make a field lookup dependent on the value in another field of a record? | Susan A | Database Design | 8 | May 22nd, 2004 09:10 PM |