numero = 23742
interpreted = N
texte = >Hey guys! Has anyone had to deal with color options for database items >with WebCatalog? > >I have a database (~200 items) of items that each have their own color >options (2-6 colors for each item). When someone wants to buy an item, >they have to choose the color. Each item has unique colors, and each has >a different number of color options as well. > >I'm new to this, and I don't know how to have WebCatalog handle this. >Can anyone provide ideas?? > >Teresa L. Schmidt >The Northwoods.com >You connection to Northern Wisconsin begins with www.thenorthwoods.com! >(715) 356-7399 >Fax: (715) 358-8886 >teresa@thenorthwoods.comTeresa-I have actually just set up a fairly intense WebCat-based shopping cart system that does this. Without writing a novel, here how it works:1) Each product in my catalog has information that remains the same, no matter what size or color it is (name, description, etc.). All of this info is kept in one db called products.db Each product listed in the products.db has a minsku value that is unique to each product.2) I have several other db's that are named: manufacturer.db, size.db and color.db that consist of two fields manid and manname or sizeid and sizename or colorid and colorname These are how I map the variable names to their associated id.3) I then created another db called price.db that stores the following info: - sku (this is autogenerated by combining the [manid]-[minsku]-[colorid]-[sizeid]) - colorid (obvious) - sizeid (obvious) - price (price for this specific sku... in my catalog, prices can change based on size) - minsku (obvious) - weight (to be used for calculating shipping charges, and for back-end purposes)4) On my product detail page, I have a whole lot of lookups and sub-searches that occur that generate an