Thanks, I will work through it today (and hopefully get cbo2 to do what I tell it to do!). I only recently began on this creating applications journey. I have some programming experience but I am totally new to Access. Setting up the proper tables and creating the proper relationships has...
Regarding my file and tables, a lot of what you see is just testing and trials while I learn different things about Access. They are not permanent nor is everything being used.
We are in the clothing recycling business. We send out trucks daily to collect clothes, we also purchase clothes...
Hmmm. :banghead: I think, when I designed the query, Access put those Row Sources in the Lookups for the fields in the junction table - I'm pretty sure I didn't do that (at least not on purpose!). What is an alternative method to lookups at table field level?
Thanks for your help so far.
When I add that routine the message shows the name in the cboWLocation.
I was looking for the number in the ID field (in the same table) corresponding to that location. For example, if the cboWLocation was 'cages' I would want to have the number 1, if it was 'garbage' then the number 35...
Hope I did this upload correctly. The zip file is attached.
Please note that I am very new to Access, so, there is a lot of testing in the file and it is quite 'messy'. There are extra queries and forms and vba coding. The form that has the 2 comboboxes is frmInventoryReceivedInput.
Thanks, jdraw. Excellent videos. I have no problem when there is a simple relationship between 2 tables. The problem has only come up when there is a many-to-many relationship with a junction table.
I am having trouble with my drop down list in a second combobox. I have 3 tables as follows:
Table 1: s, fields: Source _ID(pk), Source _Name
Table 2: w, fields: Location_ID(pk), Location_Name
Table 3 (junction table): sw, fields: SW_ Source _ID(pk), SW_Location_ID(pk)
I have 2 comboboxes on...