>Hi,
>
>although this is a VFP application, the problem is not really VFP related. Currently I have items that can be sold and multiple of those items can be added to an invoice (invoice line items). I want to allow the user to combine multiple of those items into one item that can then be sold with its own unique price (which is not necessarily a sum of all the prices of the individual components). What terminology is used to describe this? I'm thinking Bill Of Materials, but that doesn't "feel" quite right.
>
>I am guessing that the data structure I need to implement is like this:
>
>Items
>ItemId
>ItemDescription
>ItemPrice
>
>ItemsSub
>ItemsSubId
>ItemId
>ItemQty
>
>Does that make sense?

From your perspective look at the inventory of items maintained as simply "items", whether they are assemblies or singular, whether some may only be components and others are final products. If an "item" is actually an assembly (such as a kit containing a lens and whatever else) that may be apparent by the item description the end user assigns. I say "may" because the user might choose to simply call a product constituting a million parts something like "jet plane". Meanwhile, returning to the computer application, all items in the inventory are simply items. There might be an indication that something or the other is commonly used as a component, or is a final product consisting of no sub-assemblies. The final determinant of "is something a component or final product" is determined by the presence of a bill of materials for that item. If you are not using a bill of materials system to calculate inventory usage and costs then you're in for a bumpy ride.