Tony,
I'm currently working on the same thing but have decided to make BOM's
a separate entity and not an item in the item file. Thus I have an
Assembly table that has many Assyitems. These Assytitems hold foreign
keys to the Item table. This works well when users don't have to do
nested BOM's.
Kathleen
thanks for the suggestion. I thought about pulling BOM out to a
separate model that would be used to reference the BOM Items. I went
backwards and forwards a few times and decided to try it with just the
bom_items and see if I was losing any functionality. Still putting
together the view to allow BOMs to be created for a product, I will
see how it works out.
(please think of better names than I have
Then given a production, p.components are the products it is made of,
and p.uses is the products that uses it as a component