Viv,

You are right of course. I had a client who wanted his existing app redone (done by the previous developer) and I was flabbergasted with how the products table was done ('flat-file'ish as per your words). Anyhow, I posted this thread to see if this is ever done by anybody else.

Thanks a lot. Cheers!

Dennis

>The solution probably depends on the percentage of items where this occurs. If the frequency is low I'd use the first option. I don't think I'd consider the second option at all - too inflexible (and 'flat-file'ish).
>
>The *most* flexible option may be the old 'component/assembly' design using three tables (ideally allowing an assembly list to recursively contain other assemblies as well as components)
>:
>

>Components:
>1 Coke 333 ml
>2 Coke 1   ltr
>3 Potato Chips
>4 Sandwich
>etc...
>
>Assemblies (Inventory Items)
>ID  Name     etc
>....
>3 12 x 1Litre Coke Pack
>4  6 x 1Litre Coke Pack
>5 Large Coke with free chips
>6 Deluxe Picnic Hamper
>
>Assembly List
>AID Component  Assembly  Quan
>3   2                    12
>4   2                    6
>5   2                    1
>5   3                    1
>6                5       1
>6   4                    1
>

>etc. HTH,
>Viv