Combobox not populating

[Danielt949]

Good evening all.

Can someone please have a look at my project. For some reason, it does not matter what i do, my combo box will not populate with query, It keeps giving a blank.

Ive even tried copy and pasting from another working query and changing a few things and it still wont work.



The form i am needing looked at is Frm_New_Defect
The function should be....

1. Select "Saraji" from Location combobox, this then populates "Asset Type" combobox (Working perfectly)
2. Select "Drill" from Asset Type combobox, This then SHOULD populate the "Category" combobox
3. Category combobox should populate using Asset Type combobox as the criteria. (This is the part that returns only blank results)

To filter this information, i am using the table Tbl_Categories, Adding Asset Type and Category into the query, filtering the Asset type criteria using the Asset type combobox on Frm_New_Defect.

Can someone please have a look and see where i am going wrong. I dont understand as there are a couple similar query using the Tbl_Categories as its base information and they are working perfect.

Please also understand i am not too familiar with the use of the SQL sides of things, generally using the query wizard as this is "Normally" doing what i need of it for now.

Cheers.
CMMS-2.zip

[Welshgasman]

Run the query first.
Does that produce any data?

[Micron]

I tried to look at it. Almost every time I switch your form from design to form view the db crashes. What I did find is that if you remove the reference to the category combo in the query and replace it with the number 1 it works. I suspect that you need to add the CategoryID from table categories and make that the first field in the query. Then your category combo should work.

All of your combos seem to be retrieving the wrong fields. Don't use the text values like "Saraji" - use the pk fields from those tables (the autonumber id fields).

[Micron]

Everywhere I've looked, you're getting your combo values from the wrong tables and/or fields. Example - location combo should get list rows from location table. You hide id column and show location name column. User picks Saraji and the combo "stores" ID 1. Location ID values should be a long integer field in the next table, right beside that table's ID field. So table asset location should store the value of 1, not Saraji.

I think you need to review db normalization to understand what I'm trying to say (and not doing a great job of it).