Re: Search Combining Problem

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 57981
interpreted = N
texte = Try adding "&REMARKS1word=ww" so it will only match "whole words". - brian On May 24, 2004, at 8:12 AM, Jesse Crofoot wrote: > Looks like that did the trick for the most part, however I'm still > having > problems with the search. The problem I'm running into now is one of > the > lakes is simply named "Big" and there are a few lakes with "Big" in > the name > so those are being found by the search as well. Any other suggestions > on > how to hammer down the search. Below is my full search code. > > [search > db=^MLSData/ > lakechains.db&eqLAKECHAIN_CHAINdatarq=[LAKECHAIN]&LAKECHAIN_LAKE > sort=1] > > [search > db=^MLSData/ > mls.db&REMARKS1wbrk=,&woREMARKS1datarq=[founditems][LAKECHAIN_LA > KE][hideif > [INDEX]=[NUMFOUND]],[/hideif][/ > founditems]&LISTPRICEtype=num&LISTPRICEsort=1 > &max=15] > > > ----- Original Message ----- > From: "Erol Guneri" > To: "WebDNA Talk" > Sent: Monday, May 24, 2004 8:39 AM > Subject: Re: Search Combining Problem > > >> Hi Jesse, >> >> I think you need to add &REMARKS1wbrk=, to your search string so that >> it >> knows what the seperator is, making your search string: >> >> [search db=^MLSData/mls.db&wsREMARKS1data=[url]LAKE/RIVER: Little >> Tomahawk,LAKE/RIVER:Minocqua[/url] >> &REMARKS1wbrk=,&LISTPRICEtype=num&LISTPRICEsort=1&max=15] >> >> Erol >> >> >> ----- Original Message ----- >> From: "Jesse Crofoot" >> To: "WebDNA Talk" >> Sent: Monday, May 24, 2004 2:24 PM >> Subject: Search Combining Problem >> >> >>> Hello all, >>> >>> I'm having a problem with a combined search. I've read over the >> information >>> in the guide however, the search is not doing what I'm attempting to >>> do. >>> What I'm trying to accomplish is a search in a field called Remarks1 >>> for >>> several different lake names. below is the search code I'm working > with. >>> This is my test code not the final search as it will be generated by >>> a >>> database search to determine the lakes belonging in a given lake >>> chain. >>> Here is my test search code. >>> >>> [search db=^MLSData/mls.db&wsREMARKS1data=[url]LAKE/RIVER: Little >>> Tomahawk,LAKE/RIVER: >>> Minocqua[/url]&LISTPRICEtype=num&LISTPRICEsort=1&max=15] >>> >>> If I remove the 2nd item LAKE/RIVER: Minocqua, the search works >>> properly >>> returning only the properties listed that are on Little Tomahawk. > However >>> with the 2nd item in the search I'm getting 0 found. Any >>> suggestions on >>> this will be greatly appreciated. >>> >>> Jesse L Crofoot >>> Web Designer >>> By Request Web Designs >>> & HodagSports.Com >>> jesse@hodagsports.com > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.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:

    
  1. Re: Search Combining Problem ( "WebDna @ Inkblot Media" 2004)
  2. Re: Search Combining Problem ( "Jesse Crofoot" 2004)
  3. Re: Search Combining Problem ( Jesse Proudman 2004)
  4. Re: Search Combining Problem ( "Jesse Crofoot" 2004)
  5. Re: Search Combining Problem ( Brian Fries 2004)
  6. Re: Search Combining Problem ( "Jesse Crofoot" 2004)
  7. Re: Search Combining Problem ( Brian Fries 2004)
  8. Re: Search Combining Problem ( "Jesse Crofoot" 2004)
  9. Re: Search Combining Problem ( "Erol Guneri" 2004)
  10. Search Combining Problem ( "Jesse Crofoot" 2004)
Try adding "&REMARKS1word=ww" so it will only match "whole words". - brian On May 24, 2004, at 8:12 AM, Jesse Crofoot wrote: > Looks like that did the trick for the most part, however I'm still > having > problems with the search. The problem I'm running into now is one of > the > lakes is simply named "Big" and there are a few lakes with "Big" in > the name > so those are being found by the search as well. Any other suggestions > on > how to hammer down the search. Below is my full search code. > > [search > db=^MLSData/ > lakechains.db&eqLAKECHAIN_CHAINdatarq=[LAKECHAIN]&LAKECHAIN_LAKE > sort=1] > > [search > db=^MLSData/ > mls.db&REMARKS1wbrk=,&woREMARKS1datarq=[founditems][LAKECHAIN_LA > KE][hideif > [INDEX]=[NUMFOUND]],[/hideif][/ > founditems]&LISTPRICEtype=num&LISTPRICEsort=1 > &max=15] > > > ----- Original Message ----- > From: "Erol Guneri" > To: "WebDNA Talk" > Sent: Monday, May 24, 2004 8:39 AM > Subject: Re: Search Combining Problem > > >> Hi Jesse, >> >> I think you need to add &REMARKS1wbrk=, to your search string so that >> it >> knows what the seperator is, making your search string: >> >> [search db=^MLSData/mls.db&wsREMARKS1data=[url]LAKE/RIVER: Little >> Tomahawk,LAKE/RIVER:Minocqua[/url] >> &REMARKS1wbrk=,&LISTPRICEtype=num&LISTPRICEsort=1&max=15] >> >> Erol >> >> >> ----- Original Message ----- >> From: "Jesse Crofoot" >> To: "WebDNA Talk" >> Sent: Monday, May 24, 2004 2:24 PM >> Subject: Search Combining Problem >> >> >>> Hello all, >>> >>> I'm having a problem with a combined search. I've read over the >> information >>> in the guide however, the search is not doing what I'm attempting to >>> do. >>> What I'm trying to accomplish is a search in a field called Remarks1 >>> for >>> several different lake names. below is the search code I'm working > with. >>> This is my test code not the final search as it will be generated by >>> a >>> database search to determine the lakes belonging in a given lake >>> chain. >>> Here is my test search code. >>> >>> [search db=^MLSData/mls.db&wsREMARKS1data=[url]LAKE/RIVER: Little >>> Tomahawk,LAKE/RIVER: >>> Minocqua[/url]&LISTPRICEtype=num&LISTPRICEsort=1&max=15] >>> >>> If I remove the 2nd item LAKE/RIVER: Minocqua, the search works >>> properly >>> returning only the properties listed that are on Little Tomahawk. > However >>> with the 2nd item in the search I'm getting 0 found. Any >>> suggestions on >>> this will be greatly appreciated. >>> >>> Jesse L Crofoot >>> Web Designer >>> By Request Web Designs >>> & HodagSports.Com >>> jesse@hodagsports.com > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.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/ Brian Fries

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:

Proper file locations (1997) [WebDNA] OAuth - anybody done this yet? (2009) READFILE command? (1998) Warning: Mac OS X 10.2.4 Update Overwrites Apache's (2003) CommandSecurity? (1997) WebMerchant Question (2000) French characters in variables (2001) Carrying over data? (1997) Proper file locations (1997) textarea text truncated by browser (2000) Ram WebDNA is using (2004) Password protect (2000) Instructions for Digest (1997) New command suggestion (1997) (2001) Secure server question (1997) test (2004) [Semi-OT] Eaaaaaasy OSX FTP (2003) Re[2]: Support suggestions - Response (2000) Counting Inventory (2003)