Combo Boxes on a subform

[reverentcreature]

Hi all ,

Im making a database to log and close down calls for a security company. I have a closedown form for the Jobs table for entering the job details and subform on this for the JobParts which links the Parts to the job so that quantity and price etc can be added.

Currently you can type in the PartID into this subform to pull in a Part that was fixed/installed but my friend would like to be able to filter the PartMake field and then select a PartModel. Both make and model are fields in the Parts table so I can add them to the subform without any problems. But Im not sure how to get them to filter correctly. I may be missing something obvious.

I have looked around and seen examples of queries and even considered making new table and relationship called Manufacturer (which might contain the make) but I think this might be an overkill. Im pretty sure I need to make combo boxes but Im not sure how.

Has anyone set up filtering or used combo boxes to add records to subform before?

 

[Alansidman]

Take a look at this page. There are three videos on Combo Boxes. They will help you to create what you need.

http://www.datapigtechnologies.com/AccessMain.htm

If you are still having difficulties, come back with your specific questions.

Alan

 

[reverentcreature]

Hi Alan,

Thanks for the link. It was very informative. I think Im on the right lines. But the tutorial uses a blank form with two unbound combos. Im not sure how to incorporate that into my database. Currently a user enters the PartID into the foreign key for JobPartsPartID in the JobParts table.

Do I need an unbound combo for Make to filter the JobPartsPartID foreign key field? Or should I hide the Part ID column by adding a second column to the combo? I have tried several things but to no avail.

 

[ozmo]

Your bound (to table.column) combobox will only work for a static list; that is, all the rows of your column will always be listed. If you want the combobox values to depend on some variable criteria, then you will have to either bind it to a saved query or assign its Row Source to a query that you build in VBA. I recommend the latter as it is less messy.