Re: Number searching/formats
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16560
interpreted = N
texte = >> >>-------------------- Original Message Follows -------------------- >>>>rnpricedata=[form.minprice] [form.maxprice]&pricetype=num >>>> >>>>works great... No problem! However, it does not display records with the >>>>price format including a comma. i.e. 2,999 etc.... if the format is >>>>2999.00, 2999, no problem. >>>> >>>>Is it possible to format the numeric value at the point of input???? >>> >>> >>>No, your visitor has complete control over the value that gets entered >>into the form. You have to pass that value to the next page, where you can >>perform your append or replace. Then, instead of putting a simple >>[form.price] tag inside the append or rep >>> >>>lace context, you can put that tag inside a [format] context first. The >>format context can be used to change the form value into the proper format >>*before* it gets placed into the database. Then your comparisons will work >>fine ... :) >>> >> >I played with the format feature right after sending the email, however the >results were: > >price=[format 10.2f][form.price][/format] > >if the value entered was 19,000. the value saved would be 19.00. (BAD) >if the value entered was 19000 the value saved would be 19000.00. (GOOD) > >Any ideas???Sure, don't let your users enter punctuation into that field ... :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Associated Messages, from the most recent to the oldest:
>> >>-------------------- Original Message Follows -------------------- >>>>rnpricedata=[form.minprice] [form.maxprice]&pricetype=num >>>> >>>>works great... No problem! However, it does not display records with the >>>>price format including a comma. i.e. 2,999 etc.... if the format is >>>>2999.00, 2999, no problem. >>>> >>>>Is it possible to format the numeric value at the point of input???? >>> >>> >>>No, your visitor has complete control over the value that gets entered >>into the form. You have to pass that value to the next page, where you can >>perform your append or replace. Then, instead of putting a simple >>[form.price] tag inside the append or rep >>> >>>lace context, you can put that tag inside a
[format] context first. The >>format context can be used to change the form value into the proper format >>*before* it gets placed into the database. Then your comparisons will work >>fine ... :) >>> >> >I played with the format feature right after sending the email, however the >results were: > >price=[format 10.2f][form.price][/format] > >if the value entered was 19,000. the value saved would be 19.00. (BAD) >if the value entered was 19000 the value saved would be 19000.00. (GOOD) > >Any ideas???Sure, don't let your users enter punctuation into that field ... :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Kenneth Grome
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:
calculating tax rates, mail order solutions and version 2 (1997)
Re:2nd WebCatalog2 Feature Request (1996)
[WebDNA] CSS HTML Email Using Emailer (2010)
Wanted: More Math Functions (or, Can You Solve This?) (1997)
WebCatalog 4.0 has been released! (2000)
View order not right (1997)
Re:Help name our technology! (1997)
international time (1997)
TCPConnect / Current Temperature (2004)
WebCatalog 4.0 has been released! (2000)
service stop and restart (1997)
Arrays (2000)
WC2b15 File Corruption (1997)
[WebDNA] Domain upgrade questions (2009)
JPG Force Download - BUG? (2007)
Search context not finding recent entries (1998)
More DateMath problems (1997)
Tax Moratorium Expiring (2001)
RE: Problems reading files created by WC (1997)
Using webcat to roll apache logs (2002)