When I set up lookup fields that point to a table do I save those tables in the back end with the main tables or is it okay to have in in the front end and not the back end? Users will need to make udpates to the tables for instance an employee table they would need to add employee names. What is the correct way? TIA
Setting up lookup fields (1 Viewer)
- Thread starter Angel69
- Start date
RuralGuy
AWF VIP
- Local time
- Today, 15:19
- Joined
- Jul 2, 2005
- Messages
- 13,826
I hope you have read this link already: http://access.mvps.org/access/lookupfields.htm
- Local time
- Today, 22:19
- Joined
- Jul 9, 2003
- Messages
- 16,363
A normal lookup table will consist of an ID field and a description field, in other words only two fields. (A developer would use 3+ fields)
The normal way to extract the lookup information is to use a combobox and only store the ID field from the look-up table.
The normal way to allow the user to add items into a lookup table is to set the combobox (as described above) set its "not in list" event to add a record to the lookup table. (The "not in list" event is easy to setup in MS Access 2007 and up)
The normal way to extract the lookup information is to use a combobox and only store the ID field from the look-up table.
The normal way to allow the user to add items into a lookup table is to set the combobox (as described above) set its "not in list" event to add a record to the lookup table. (The "not in list" event is easy to setup in MS Access 2007 and up)
Last edited:
