If you have 2400 possible door combinations and have all the variables in those records, then why would your subform need inputs for those variables as opposed to a search form that locates the door ID based on the required inputs? I presume the combinations table includes a pricing field, so a quote table has the quoteID, comboId and the price, reflecting any discounts. Your invoice should be able to grab all the options from the combos table fields. Not sure where the individual options prices might be coming from, or even if you need them. If I'm way off base, it should illustrate that to fully understand the design goal involves far more details than what you've revealed thus far.
You are in for a rough ride by taking on something like this for your first project. The do's and dont's about naming things, reserved words, autonumbers, normalization, lookup fields, multi value fields etc. etc. are daunting enough for a newcomer and a small project. If I had one statement about design, it would be to learn the basics, then get some flip chart sized paper and design the relationships on that - with pencil.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.