Re: Repeating Fields

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12951
interpreted = N
texte = >I need to store along with each SKU, a list of modifiers (in my case >Keys) which modify the product. For instance, Song X can be purchased in >8 different keys. On the results page I want to have the user use a >pop-up menu to select the key for a song, which will be transferred to >TextA for the cart when they Add. Should I just create a database which >looks something like:how about first figuring out the maximum amount of keys a song would have. Then for each sku (song), have fields like this: key1 key2 ... keyN. Now when you list the options, use this:Pick a Key: This would show the keys ONLY if you inputted them into the database. If the song came in only one, just that would show. You could use this for displaying the available keys as well.Aloha,Olin..................................................................... W O R L D P O I N T I N T E R A C T I V E OLIN KEALOHA LAGON director, website creation Honolulu San Francisco 2800 woodlawn drive 222 sutter street olin@worldpoint.com suite 170 sixth floor www.worldpoint.com honolulu, hi 96822 san francisco, ca 94108 voice.808.539.3978 fax.808.539.3943 cell.808.291.1610 ..................................................................... Associated Messages, from the most recent to the oldest:

    
  1. Re: Repeating Fields (Grant Hulbert 1997)
  2. Repeating Fields (netmouse@summit1.com (Anne K. Gay) 1997)
  3. Re: Repeating Fields (Grant Hulbert 1997)
  4. Re: Repeating Fields (Olin 1997)
  5. Repeating Fields (Michael Bohan 1997)
>I need to store along with each SKU, a list of modifiers (in my case >Keys) which modify the product. For instance, Song X can be purchased in >8 different keys. On the results page I want to have the user use a >pop-up menu to select the key for a song, which will be transferred to >TextA for the cart when they Add. Should I just create a database which >looks something like:how about first figuring out the maximum amount of keys a song would have. Then for each sku (song), have fields like this: key1 key2 ... keyN. Now when you list the options, use this:Pick a Key: This would show the keys ONLY if you inputted them into the database. If the song came in only one, just that would show. You could use this for displaying the available keys as well.Aloha,Olin..................................................................... W O R L D P O I N T I N T E R A C T I V E OLIN KEALOHA LAGON director, website creation Honolulu San Francisco 2800 woodlawn drive 222 sutter street olin@worldpoint.com suite 170 sixth floor www.worldpoint.com honolulu, hi 96822 san francisco, ca 94108 voice.808.539.3978 fax.808.539.3943 cell.808.291.1610 ..................................................................... Olin

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:

bad idea to not use any html files, only .tpl files? (1999) Newbie problem blah blah blah (1997) Line Feed problems ... (2002) [WebDNA] v7 Stress Test and Strange Behaviour (2012) Help Wanted - Stowe, Vermont (1999) HELP! Search finding too much! (1998) Multiple Pulldowns (1997) Hiding usernames and passwords in URL (1998) multiple search commands (1997) [CART] inside a [LOOP] (1997) Bug alert! (1997) Bad suffix error (1997) [date format] w/in sendmail (1997) Multiple Merchant Accounts? (1997) [WebDNA] unix timestamp in WebDNA (2009) includes and cart numbers (1997) Separate SSL Server (1997) TCPConnect Help (2003) [OT] friday pics :-) (2005) setting line item numbers (1998)