Re: Nesting format tags

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11647
interpreted = N
texte = >We're just too demanding, aren't we? Actually, what I have is a set >number of fields for product information in an order form (so it imports >into the client's order fulfillment software), i.e. 15 records, each >with a length of 37, so if a customer orders 15 items, all of the spaces >will be filled, but if they only order 1, then the remaining 14 record >spaces have to be filled with blank spaces. In other words, it has to >be 555 characters in length no matter what. OK, well I know it's harder than just using 555s, but you can certainly use the 255 + 300 trick I mentioned earlier.Or you can get real tricky with [math] and [showif] inside the [lineitems] loop -- there should be something like [numlineitems] that tells you how many items are in the cart, so you could multiply that by 37 to see how many you have already written out, then pad the remainder with 555-37*numLineItems. Something like that. Sounds like programming because it is.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Nesting format tags (Grant Hulbert 1997)
  2. Re: Nesting format tags (John S. Winningham 1997)
  3. Re: Nesting format tags (Grant Hulbert 1997)
  4. Re: Nesting format tags (John S. Winningham 1997)
  5. Re: Nesting format tags (Kenneth Grome 1997)
  6. Re: Nesting format tags (Grant Hulbert 1997)
  7. Nesting format tags (John S. Winningham 1997)
>We're just too demanding, aren't we? Actually, what I have is a set >number of fields for product information in an order form (so it imports >into the client's order fulfillment software), i.e. 15 records, each >with a length of 37, so if a customer orders 15 items, all of the spaces >will be filled, but if they only order 1, then the remaining 14 record >spaces have to be filled with blank spaces. In other words, it has to >be 555 characters in length no matter what. OK, well I know it's harder than just using 555s, but you can certainly use the 255 + 300 trick I mentioned earlier.Or you can get real tricky with [math] and [showif] inside the [lineitems] loop -- there should be something like [numlineitems] that tells you how many items are in the cart, so you could multiply that by 37 to see how many you have already written out, then pad the remainder with 555-37*numLineItems. Something like that. Sounds like programming because it is.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

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:

[WebDNA] [announce] WebDNA 6.2.1x (2012) Large founditems loops (2000) [OT] Changing permissions on W2003 via FTP (2007) test (2003) Help! WebCat2 bug (1997) Converting spaces to + in results list (2000) docs for WebCatalog2 (1997) Separate SSL Server (1997) carts on MacOS X Server (2000) Deleting with contexts (2001) search for non-unique question (2001) Math Context (1998) Trouble with formula.db (1997) Bug Report, maybe (1997) The List is Changing (1997) Error Lob.db records error message not name (1997) [Sum] function? (1997) emailer w/F2 (1997) emailer on Windows Beta 18 (1997) Date problems (1997)