Hello gang
I have started an access project and after searching the forum, I have a couple questions on table structure.
Questions:
I've read in several threads that I should NOT use any type of "Lookup" in a table structure. No "Combo Boxes", or "Value List", period.
I understand but why?
Not using a âLookupâ in table1, I will create table2 with the lookup values I want to store in table1. Utilizing a form, I create a combo box. The âControl Sourceâ of the combo box will be the field in table1 that I want to put the data into, and the âRow Sourceâ will be a query based on the values I entered in table2.
Am I correct thus for?
Assuming this is the correct way to format a lookup. What is the best and easiest way to enable the user to update this list without giving the user access to the table holding the values, a separate form?
If all this is correct, I will have lots of tables storing lookup values and lots of forms for the user to update these lists when needed.
Is there an easier, better, or cleaner way to accomplish this task?
Sum it all up example:
In tbl_Equipment contains the field âStatusâ. The data type is âShort Textâ.
In tbl_Status contains the StatusID field, (AutoNumber) and the filed âStatusâ with the data type as âshort Textâ that will contain the list of statuses. The frm_Equipment based on tbl_Equipment will contain a combo box. The control source of the combo box will be from tbl_Equipment, âStatusâ field. The row source is the query based on the tbl_Status for the values.
I will have a multitude of these lookup(s) for various form combo boxes.
Is there a better way as to not create a table for each lookup value and a form for each look value table for updating each list?
Stand by! More questions to come!
-Kyp
I have started an access project and after searching the forum, I have a couple questions on table structure.
Questions:
I've read in several threads that I should NOT use any type of "Lookup" in a table structure. No "Combo Boxes", or "Value List", period.
I understand but why?
Not using a âLookupâ in table1, I will create table2 with the lookup values I want to store in table1. Utilizing a form, I create a combo box. The âControl Sourceâ of the combo box will be the field in table1 that I want to put the data into, and the âRow Sourceâ will be a query based on the values I entered in table2.
Am I correct thus for?
Assuming this is the correct way to format a lookup. What is the best and easiest way to enable the user to update this list without giving the user access to the table holding the values, a separate form?
If all this is correct, I will have lots of tables storing lookup values and lots of forms for the user to update these lists when needed.
Is there an easier, better, or cleaner way to accomplish this task?
Sum it all up example:
In tbl_Equipment contains the field âStatusâ. The data type is âShort Textâ.
In tbl_Status contains the StatusID field, (AutoNumber) and the filed âStatusâ with the data type as âshort Textâ that will contain the list of statuses. The frm_Equipment based on tbl_Equipment will contain a combo box. The control source of the combo box will be from tbl_Equipment, âStatusâ field. The row source is the query based on the tbl_Status for the values.
Code:
SQL: SELECT DISTINCTROW Status.* FROM Status ORDER BY Status.Status;)
I will have a multitude of these lookup(s) for various form combo boxes.
Is there a better way as to not create a table for each lookup value and a form for each look value table for updating each list?
Stand by! More questions to come!
-Kyp