Re: Price spread

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 44072
interpreted = N
texte = James, try:[search db=.db&eqPRODUCT_PICdatarq=[pic]&asPRICEsort=1&PRICEtype=num] [founditems] [showif [price]<180.01] [showif [price]>99.99] [/showif] [/showif] [/founditems]
PICDESCRIPTIONPRICE
[pic][desctiption]$[format .2f][PRICE][/format]buy
[/search]if all you need is to show only those with a price of 100,140 or 180, us this in place of both those showif's:[showif _100_140_180_^_[price]_]Donovanyou can also do this in the search comparisons using group fields I believe.James Murtagh Jewellers wrote:> Hi there > > I am finishing a revamp on my site and would like help to provide the > customer with the spread of prices for products in the form > > Prices from $100 - $180 > > ignoring each price between the lowest and the highest. > > The listing for a product is based on the photo code [pic], a > simplified example is below > > pic description price > cj131 10kt Gold Celtic Wedding Band $100 > cj131 14kt Gold Celtic Wedding Band $140 > cj131 18kt Gold Celtic Wedding Band $180 > > I would be grateful for any help with this as I'm getting tight on time. > > JAMES MURTAGH > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Price spread (Pat McCormick 2002)
  2. Re: Price spread (Glenn Busbin 2002)
  3. Re: Price spread (Donovan Brooke 2002)
  4. Price spread (James Murtagh Jewellers 2002)
James, try:[search db=.db&eqPRODUCT_PICdatarq=[pic]&asPRICEsort=1&PRICEtype=num] [founditems] [showif [price]<180.01] [showif [price]>99.99] [/showif] [/showif] [/founditems]
PICDESCRIPTIONPRICE
[pic][desctiption]$[format .2f][PRICE][/format]buy
[/search]if all you need is to show only those with a price of 100,140 or 180, us this in place of both those showif's:[showif _100_140_180_^_[price]_]Donovanyou can also do this in the search comparisons using group fields I believe.James Murtagh Jewellers wrote:> Hi there > > I am finishing a revamp on my site and would like help to provide the > customer with the spread of prices for products in the form > > Prices from $100 - $180 > > ignoring each price between the lowest and the highest. > > The listing for a product is based on the photo code [pic], a > simplified example is below > > pic description price > cj131 10kt Gold Celtic Wedding Band $100 > cj131 14kt Gold Celtic Wedding Band $140 > cj131 18kt Gold Celtic Wedding Band $180 > > I would be grateful for any help with this as I'm getting tight on time. > > JAMES MURTAGH > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Donovan Brooke

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:

emailer settings and control questions (1997) WC2.0 Memory Requirements (1997) WC Database Format (1997) Tax & Shipping (1997) WebDNA Windows 5.0 sendmail bug (2003) RE: Renaming textA (1998) Hairy Shipping Monster (2006) Using grep to parse Canadian Postal Codes (2002) OK, here goes... (1997) RAM to disk (2002) [WebDNA] Just drop the Server version (2015) WebCatalog NT beta 18 now available (1997) WebCatalog can't find database (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) [format 40s]text[/format] doesn't work (1997) Secure Server (1997) form data submission gets truncated (1997) [WebDNA] [if] or [case] or something else (2012) Running 2 two WebCatalog.acgi's (1996) when is failing to [URL]ize values in a comparison risky? (1999)