Haha, I'm honored that my problem is so mentally stimulating.
It's actually much more complicated than I've laid out here. This system ties into inventory and cost, so there is currently a nested cost associated with each recipe. This has been implemented with multiple lookup and summary fields between Recipes and Subrecipes. (And this can go to infinite depth).
There is a scaling functionality needed as well that I haven't tackled yet. A separate table keeps track of all the recipes I'm making on a certain day and in what quantity. So if I'm making 30 bologneses on Tuesday, I would need the kitchen to make 8 oz * 30 of pasta.
That's part of why I'm trying to print out the subrecipes and ingredients for the kitchen, so they know how much of what ingredients to make on the days we are making food.
I'd be happy to go over this in more detail if you're having fun thinking about the solution, but it would probably require the entire ERD and explaining our entire business, hah. I appreciate you thinking about it though because I've been taxing my brain trying to figure out how to get a flattened list in Quickbase (while still maintaining the other database functionality we need and not duplicating data entry anywhere).
