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:
Limitations on fields? Server is crashing (1997)
[WebDNA] v.7 and eCommerce (2012)
Bug or syntax error on my part? (1997)
[format] minus figures (2003)
US Postal Service API (2007)
carriage returns in data (1997)
Adding up line items. (2000)
[BULK] RE: [WebDNA] [BULK] Should I be worried about this web (2017)
searchable list archive (1997)
multi-paragraph fields (1997)
[Middle] Probs with "&" (2003)
Reading through the Order File (1999)
Bounced Emails (2005)
Problems with cybercash (2000)
WC2.0 Memory Requirements (1997)
Warning: Mac OS X 10.2.4 Update Overwrites Apache's (2003)
Custom formulas.db (1998)
New commands in Final candidate (1997)
port 16080 problem (2003)
RequiredFields notes ... (1997)