Re: Linux Beta4 problems with multirecord returns

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 32239
interpreted = N
texte = Thanks. At least now I know I am not crazy. You could have the parser check for the existance of a parameter for [max], [min], etc. If null, then it falls back to looking for a variable named [max].The other option is using [fieldmax] instead of [max field]. I don't know how hard it would be to get the parser to to see the trailing modifier. I would find that style to be easy to understand. But of course, someone could try and name a field max, then want to find the maximum ;~(By the way, did you fix the parser to see that [date format] is different from [date] when in an orderfile context? If the parser has a way to wait for the tag closure before chosing the path, that would be preferrable.John Peacock ...waiting for Beta5GHulbert@smithmicro.com wrote: > > >It appears that the construct [max] is evil. As soon as it appears in > >any page, bad things happen, except within [FormVariables]. I added > >the following to the top of my page: > > I think I see it now. Looks like the new aggregate functions in > searches interfere with the existing max. I may have to change the > new [min field], [max field], [avg field], and [sum field] to other > names. > > Grant Hulbert, Director of Engineering ********************************** > Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) > 16855 West Bernardo Drive, #380 | ------------------------- > San Diego, CA 92127 | Software & Site Development > Main Line: (858) 675-1106 | http://www.smithmicro.com > Fax: (858) 675-0372 ********************************** > > ########################################################################################################################## 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 To switch to the INDEX mode, E-mail to Send administrative queries to Associated Messages, from the most recent to the oldest:

    
  1. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  2. Re: Linux Beta4 problems with multirecord returns (GHulbert@smithmicro.com 2000)
  3. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  4. Re: Linux Beta4 problems with multirecord returns (GHulbert@smithmicro.com 2000)
  5. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  6. Re: Linux Beta4 problems with multirecord returns (GHulbert@smithmicro.com 2000)
  7. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  8. Linux Beta4 problems with multirecord returns (John Peacock 2000)
Thanks. At least now I know I am not crazy. You could have the parser check for the existance of a parameter for [max], [min], etc. If null, then it falls back to looking for a variable named [max].The other option is using [fieldmax] instead of [max field]. I don't know how hard it would be to get the parser to to see the trailing modifier. I would find that style to be easy to understand. But of course, someone could try and name a field max, then want to find the maximum ;~(By the way, did you fix the parser to see that [date format] is different from [date] when in an orderfile context? If the parser has a way to wait for the tag closure before chosing the path, that would be preferrable.John Peacock ...waiting for Beta5GHulbert@smithmicro.com wrote: > > >It appears that the construct [max] is evil. As soon as it appears in > >any page, bad things happen, except within [formvariables]. I added > >the following to the top of my page: > > I think I see it now. Looks like the new aggregate functions in > searches interfere with the existing max. I may have to change the > new [min field], [max field], [avg field], and [sum field] to other > names. > > Grant Hulbert, Director of Engineering ********************************** > Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) > 16855 West Bernardo Drive, #380 | ------------------------- > San Diego, CA 92127 | Software & Site Development > Main Line: (858) 675-1106 | http://www.smithmicro.com > Fax: (858) 675-0372 ********************************** > > ########################################################################################################################## 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 To switch to the INDEX mode, E-mail to Send administrative queries to John Peacock

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:

Configuring E-mail (1997) 'does not contain' operator needed ... (1997) RE: Remote administration (1998) Search group and ww (2003) A multi-processor savvy WebCatalog? (1997) problem: type 2 errors (1997) WC2b15 - [HTMLx]...[/HTMLx] problems (1997) emailer on Windows Beta 18 (1997) Enhancement Request for WebCatalog-NT (1996) [protect admin] (1997) Add to Cart & List of Products (1997) Tax Moratorium Expiring (2001) Counting LineItems (2000) Showing unopened cart (1997) Giving out error pages (1997) Looking up two prices in database? (1997) email address with spaces (2001) unable to run webcatalog locally (1998) login via cookies (2006) Trigger time setting (2002)