Re: Searching Numbers
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 58689
interpreted = N
texte = Special thanks to everyone who helped my problem. Particularly Charlie Kline. I'm not sure where he's sitting at, but he helped with the problem and despite the fact we're hundreds of miles a part, if he listened close he could have heard my profane frustration as he uncovered an error in my search string. Lesson learned, double check your syntax and then double check it again. Time...it's a terrible thing to waste. David On Jun 28, 2004, at 9:02 PM, Terry Wilson wrote: > David, > > I have an instance where I have a search for fielddata (no comparison, > no requirement) to find names in a database (not exact names; you get > a short list, then pick the one you're looking for), and it finds any > partial matches just fine. The search on the following page is simple > as can be: > > [search db=whatever.db&memberdata=[url][incomingname][/url]] > > It works fine. Brian offered up the wo and wa solution, and it should > work; I use that on keyword searches with no problems. All three ways > work fine for me (wo, wa, nothing). So to reiterate what Gary said, > there must be something else going on. > > Oh. I can point out one more thing that might be messing you up (it > has messed me up in the past: > > If the incoming variable has a value of nothing, then WebDNA will > ignore that part of the search criteria. Check the form page to make > sure your form field is indeed bringing in the user input. Or perhaps > the text variable is being reset on the page before it gets to the > search. (You didn't by any chance just upgrade from version 3 to ver. > 4 or higher?) Simply display [zipstore] right before the [search] to > see what's coming in. (I do that a lot; it tells me immediately if > there's a problem with the variable). A value of nothing is different > from a variable that is not passed at all. In that case, you'd get the > raw code of [zipstores], which would turn up no matches. An empty > field on the other hand, would display as nothing in the search, and > since you also say the search should find everything that's not > ID=[blank], then everything would be found. Note that in my simple > search above, there is no "Not equal blank" criterion, so if the box > is coming through empty, nothing is found. I must have ended up doing > that way (i.e. no comparison, no rq) because it was the only thing > that worked for what I wanted. Sometimes you have to just keep trying > all sorts of combinations. But first confirm the variables are being > passed correctly. > > Terry > > ------------------------------------------------------------- > 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://webdna.smithmicro.com/ > ------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Special thanks to everyone who helped my problem. Particularly Charlie Kline. I'm not sure where he's sitting at, but he helped with the problem and despite the fact we're hundreds of miles a part, if he listened close he could have heard my profane frustration as he uncovered an error in my search string. Lesson learned, double check your syntax and then double check it again. Time...it's a terrible thing to waste. David On Jun 28, 2004, at 9:02 PM, Terry Wilson wrote: > David, > > I have an instance where I have a search for fielddata (no comparison, > no requirement) to find names in a database (not exact names; you get > a short list, then pick the one you're looking for), and it finds any > partial matches just fine. The search on the following page is simple > as can be: > > [search db=whatever.db&memberdata=[url][incomingname][/url]] > > It works fine. Brian offered up the wo and wa solution, and it should > work; I use that on keyword searches with no problems. All three ways > work fine for me (wo, wa, nothing). So to reiterate what Gary said, > there must be something else going on. > > Oh. I can point out one more thing that might be messing you up (it > has messed me up in the past: > > If the incoming variable has a value of nothing, then WebDNA will > ignore that part of the search criteria. Check the form page to make > sure your form field is indeed bringing in the user input. Or perhaps > the text variable is being reset on the page before it gets to the > search. (You didn't by any chance just upgrade from version 3 to ver. > 4 or higher?) Simply display [zipstore] right before the [search] to > see what's coming in. (I do that a lot; it tells me immediately if > there's a problem with the variable). A value of nothing is different > from a variable that is not passed at all. In that case, you'd get the > raw code of [zipstores], which would turn up no matches. An empty > field on the other hand, would display as nothing in the search, and > since you also say the search should find everything that's not > ID=[blank], then everything would be found. Note that in my simple > search above, there is no "Not equal blank" criterion, so if the box > is coming through empty, nothing is found. I must have ended up doing > that way (i.e. no comparison, no rq) because it was the only thing > that worked for what I wanted. Sometimes you have to just keep trying > all sorts of combinations. But first confirm the variables are being > passed correctly. > > Terry > > ------------------------------------------------------------- > 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://webdna.smithmicro.com/ > ------------------------------------------------------------- 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://webdna.smithmicro.com/
David Cate
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:
2.01 upgrade problems (1997)
Updating Prices in Online Database (1999)
Individual Tax on Items (1998)
WebCat & WebTen (1997)
RE: AccountAuthorizer doesn't seem to work (1997)
[WebDNA] OT: How is this being done? Curious. (2009)
Problem (1997)
Mac: [ListFiles] bug alert (1997)
Snake Bites (1997)
Bug alert! (1997)
Members register & gain access system (1998)
OS X and cart directories (2003)
RequiredFields template (1997)
Question about replacing words (1998)
Fufillment e-mail? (1998)
RE: Can a database get stomped by simultaneous access? (1997)
Re:listfiles-looking for slick solution (1997)
WebCat b13 CGI -shownext- (1997)
[SearchString] (1998)
Multiple catalog databases and showcart (1997)