Re: color and size options

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14638
interpreted = N
texte = >Go to http://search.smithmicro.com/mailinglists.html and search for product size in the subject line. On 10/22 you should see some ideas.Grant,Archives....what a wonderful thing!!!Below are the solutions you mentioned in the archive. I believe #2 will work for size, yet #3 (the database) will probably need to be used due to many different variations for color, for each garment. Could you possible give a brief example of how #3 would work. 2) There are just a few different lists of sizes Create SizePopup1.inc, SizePopup2.inc, SizePopup3.inc, each of which have the unique lists of sizes in them. Add a field to the database called [SizeType] that indicates which type of size poup it needs, 1, 2 or 3Then use [ShowIf [needsSize]=T][include SizePopup[SizeType].inc][/ShowIf] 3) There is a huge variety of size lists, basically unique to each product Either put the literal HTML for the whole popup into a field in the database, or create a related database (linked by SKU) that has all the size listings in it for each SKU. Thank you, Ray Hatch (trying to learn at the speed of an OC-12, comprehending at the speed of about 9600 baud...) Associated Messages, from the most recent to the oldest:

    
  1. Re: color and size options (Grant Hulbert 1997)
  2. Re: color and size options / ARCHIVES (Paul Uttermohlen 1997)
  3. Re: color and size options / ARCHIVES (Grant Hulbert 1997)
  4. Re: color and size options (Raymond Hatch 1997)
  5. Re: color and size options (Grant Hulbert 1997)
  6. color and size options (Raymond Hatch 1997)
>Go to http://search.smithmicro.com/mailinglists.html and search for product size in the subject line. On 10/22 you should see some ideas.Grant,Archives....what a wonderful thing!!!Below are the solutions you mentioned in the archive. I believe #2 will work for size, yet #3 (the database) will probably need to be used due to many different variations for color, for each garment. Could you possible give a brief example of how #3 would work. 2) There are just a few different lists of sizes Create SizePopup1.inc, SizePopup2.inc, SizePopup3.inc, each of which have the unique lists of sizes in them. Add a field to the database called [SizeType] that indicates which type of size poup it needs, 1, 2 or 3Then use [ShowIf [needsSize]=T][include SizePopup[SizeType].inc][/ShowIf] 3) There is a huge variety of size lists, basically unique to each product Either put the literal HTML for the whole popup into a field in the database, or create a related database (linked by SKU) that has all the size listings in it for each SKU. Thank you, Ray Hatch (trying to learn at the speed of an OC-12, comprehending at the speed of about 9600 baud...) Raymond Hatch

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:

multipart part 2 (2004) Plain Language Manual? (1998) More questions about serial number dishing (1997) Tcp connect (2002) Authenticate and IIS (1997) New Command prefs ... (1997) [WebDNA] Clean URLS job - will pay (2010) Some Questions (1997) using WebCat for Associate Programs? (1998) A quickie question (1997) MacAuthorize order data fields WAS:How To question... (1997) RE: 2nd WebCatalog2 Feature Request (1996) Need relative path explanation (1997) sorting month by month (2004) Trouble with carts (2000) Date Math (2005) special commerce fields (1997) Bug Report, maybe (1997) WebCat2 beta 11 - new prefs ... (1997) problems with 2 tags (1997)