We don't use Spectra at the moment (wish I had a spare $15,000 laying
around...), but I can tell you the way that we tackled that problem. We
defined a table of option types (color, size, fabric, etc) and a table of
option values with foreign keys to the option types (color, red; color,
blue; size, small; size,medium ...) and then an association table that has
id's for instances of a product along with a unique combination of
option_types and option_values. The first instance of the product T-Shirt
would have a product_dtl id of 1 and the association table have records
such as (1, color, blue) (1, size, small) product_dtl id 2 would have (2,
color, blue) (2, size, medium) etc. This gives you a way to arbitrarily
define as many option types and option values you want and then product
dtl's are combinations of those items, some of which may be defined and
some may not. On the front end, you can do a step through process so that
if the user chooses a value for Color first, then you can query for all of
the option values for Size which are contained within product dtl's that
have an entry which include Color:Blue. That way you never give people an
option to choose which is not a defined product combination.
Hope that helps,
Judah
At 11:30 PM 5/16/2000 -0700, you wrote:
>Hello all,
>
> I asked this question at my CFUG meeting tonight and no one knew the
>answer. I am creating a product catalog for a web site using Allaire
>Spectra. I create a product object and an option object. So that each option
>can have it's own SKU, price, etc. What I want to do is then make each
>option have it's own set of options. So that a shirt that is red is only
>available in large, etc. My problem comes when I try to embed the option
>object within itself. I create a property using the option object and when I
>go to edit the option object and try to add a new property, the option
>property is not there. If I am totally going about this the wrong way,
>please let me know, but this is the best way I could think of to accomplish
>my goal. Here is a visual:
>
>Product: T-Shirt
> Option: BLUE
> Option: SMALL
> SKU: 001BS
> PRICE: 3.25
> Option: MEDIUM
> SKU: 001BM
> PRICE: 3.34
> Option: LARGE
> Option: RED
> Option: MEDIUM
> SKU: 001RM
> PRICE: 3.99
> Option: LARGE
> SKU: 001RL
> PRICE: 4.50
>
>Does this make sense to everyone?
>
>Any help would be greatly appreciated.
>
>Thanks,
>
>Sean O'Brien
>------------------------------------------------------------------------------
>Archives: http://www.eGroups.com/list/cf-talk
>To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
>send a message to [EMAIL PROTECTED] with 'unsubscribe' in
>the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
