Re: Database multiple selections

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 18861
interpreted = N
texte = >I'm building a site that needs to allow customers to select between >various sizes and up to 5 or 6 colors for each type of entry in the >database. Is there anyway to have a select form (drop down menu) in the >database rather then individual fields for sizes and colors of each >entry.If all of your products have an identical choice of sizes and colors, then you can put this popup in the template without needing it in the database at all.If each product needs its own set of choices, you can do a couple things, depending on the effort you want to put into it. One way is to put the literal HTML text of the popup code into each record of the database. This is perfectly legal, and although somewhat tedious, it is easily understandable. Another way is to create a second database that lists all the sizes and colors for each sku in your main database, and use embedded [search] contexts to find the right popup values.Try using search.smithmicro.com to look in the archives for product size choices in the subject, and you'll see some earlier discussion on this.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Database multiple selections (PCS Technical Support 1998)
  2. Database multiple selections (Robert Ruth 1998)
>I'm building a site that needs to allow customers to select between >various sizes and up to 5 or 6 colors for each type of entry in the >database. Is there anyway to have a select form (drop down menu) in the >database rather then individual fields for sizes and colors of each >entry.If all of your products have an identical choice of sizes and colors, then you can put this popup in the template without needing it in the database at all.If each product needs its own set of choices, you can do a couple things, depending on the effort you want to put into it. One way is to put the literal HTML text of the popup code into each record of the database. This is perfectly legal, and although somewhat tedious, it is easily understandable. Another way is to create a second database that lists all the sizes and colors for each sku in your main database, and use embedded [search] contexts to find the right popup values.Try using search.smithmicro.com to look in the archives for product size choices in the subject, and you'll see some earlier discussion on this.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ PCS Technical Support

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

2.1b3 --> way slow (1997) WebCat2_Mac RETURNs in .db (1997) Multiple fields on 1 input (1997) credit card - Revised (1997) Sku numbers (1997) Generating unique SKU from [cart] (1997) docs for WebCatalog2 (1997) webcat/webmerchant docs (1997) Displaying photo attached to first record (1997) Help formatting search results w/ table (1997) Multi vendor shop (2000) Multiple results (2001) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) Re:quit command on NT (1997) Authenticating users without dialog box (1997) Typhoon 4 -- yes or no? (2000) hideif glitch (2003) Sku numbers (1997) Templates for Customer Database? (1997) &FieldNametype=time unnecessary? (2000)