I guess to start off I'm not even sure if a subreport is what I want. I am working on a project for documenting crafting requirements for a game I play. What my report contains is a list of each Item you can build (craft) and what ingredients and tools are needed to build it. Each item you can build can use up to 3 different items and up to 2 different tools.
Where this project of mine gets complicated is that for some items, there is a tree of items needs. For example, a sniper rifle requires item 1 that you can buy, item 2 that you pick up in drops, and item 3 that you have to make. Now item 3 requires two additional items to create it. So what I would like is a nested structure that shows all items require to build a certain item.
Example:
Item: Sniper Rifle
Ing1: Copper x 2 [Drop]
Ing2: Reinforced Ball Bearing [Make]
Ing3: Carbon Steal x 3 [Buy]
Tool: Engraving Tool
Item: Reinforced Ball Bearing
Ing1: Steel x1
Ing2: Titanium x3
Tool: Stamping Tool
That's just a rough idea of how I want the report to read. Not all items you build use other items you have to build. So essentially I only need to create this subreport for records that include and item that is a [make] item. Is a subreport the way to do this? But the potential problem with a subreport is that one particular item I make may have 2 [make] items in there, so I'd need 2 subreports for that 1 item.
My other thought was to keep the primary list of ingredients and tools in a header above the detail section and then somehow code the report to display the list for ingredients and tools for child items to display in the details section.
Sorry if this is hard to follow, but any ideas and suggestions would be greatly appreciated.
Where this project of mine gets complicated is that for some items, there is a tree of items needs. For example, a sniper rifle requires item 1 that you can buy, item 2 that you pick up in drops, and item 3 that you have to make. Now item 3 requires two additional items to create it. So what I would like is a nested structure that shows all items require to build a certain item.
Example:
Item: Sniper Rifle
Ing1: Copper x 2 [Drop]
Ing2: Reinforced Ball Bearing [Make]
Ing3: Carbon Steal x 3 [Buy]
Tool: Engraving Tool
Item: Reinforced Ball Bearing
Ing1: Steel x1
Ing2: Titanium x3
Tool: Stamping Tool
That's just a rough idea of how I want the report to read. Not all items you build use other items you have to build. So essentially I only need to create this subreport for records that include and item that is a [make] item. Is a subreport the way to do this? But the potential problem with a subreport is that one particular item I make may have 2 [make] items in there, so I'd need 2 subreports for that 1 item.
My other thought was to keep the primary list of ingredients and tools in a header above the detail section and then somehow code the report to display the list for ingredients and tools for child items to display in the details section.
Sorry if this is hard to follow, but any ideas and suggestions would be greatly appreciated.
