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:

Hiding HTML and page breaks (1997) Passing Username and Password on the command line (2000) Resume Catalog ? (1997) Copyright ? (1997) What am I missing (1997) 2.1b3 --> way slow (1997) Format 1.15 to 1:15:00 or 01:15:00 (2002) Pull Down Search (2000) shipping with weigth (1998) Crash Log Question (2006) Mime Headers for Mail (1998) Which Pref is faster? (1998) Re[3]: 2nd WebCatalog2 Feature Request (1996) Spiders and Bots (2000) Username/Password with [Protect] (2000) Languages (1997) Subject: SMSI, please fix the StandardConversions.db (2005) wrong authentication (1998) [WebDNA] v.7 and eCommerce (2012) Simultaneous Users (1999)