Re: Search Combining Problem

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 57983
interpreted = N
texte = One more... Try adding "&REMARKS1fbrk=," - this will tell WebDNA how to break the FIELD into words, as opposed to wbrk which tells how to break the passed-in-value into words. - brian On May 24, 2004, at 9:55 AM, Jesse Crofoot wrote: > Still picking up anything with the word "Big" in the REMAKS1 field. I > have > simplified the search by dropping the 1st search that determines the > lakes > in a given lake chain and have writen direct search code for one of the > chains. Below is the search, any other ideas or suggestions will be > greatly > appreciated. > > > [search > db=^MLSData/ > mls.db&REMARKS1word=ww&REMARKS1wbrk=,&wsREMARKS1datarq=Big,Mamie > ,West Bay&LISTPRICEtype=num&LISTPRICEsort=1&max=15] > > > > ----- Original Message ----- > From: "Brian Fries" > To: "WebDNA Talk" > Sent: Monday, May 24, 2004 10:59 AM > Subject: Re: Search Combining Problem > > >> 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)
One more... Try adding "&REMARKS1fbrk=," - this will tell WebDNA how to break the FIELD into words, as opposed to wbrk which tells how to break the passed-in-value into words. - brian On May 24, 2004, at 9:55 AM, Jesse Crofoot wrote: > Still picking up anything with the word "Big" in the REMAKS1 field. I > have > simplified the search by dropping the 1st search that determines the > lakes > in a given lake chain and have writen direct search code for one of the > chains. Below is the search, any other ideas or suggestions will be > greatly > appreciated. > > > [search > db=^MLSData/ > mls.db&REMARKS1word=ww&REMARKS1wbrk=,&wsREMARKS1datarq=Big,Mamie > ,West Bay&LISTPRICEtype=num&LISTPRICEsort=1&max=15] > > > > ----- Original Message ----- > From: "Brian Fries" > To: "WebDNA Talk" > Sent: Monday, May 24, 2004 10:59 AM > Subject: Re: Search Combining Problem > > >> 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:

Redirect frame targets (1998) Updating product information (2002) SiteEdit Pro Update Announcement (1997) Autonumber in Table (2006) Setting up WebCatalog with Retail Pro data (1996) [WebDNA] DNA hosting and/or Image server Hosting. (2011) [Sum] function? (1997) I've been thinking (2002) WebCatalog 2.0 & WebDNA docs in HTML ... (1997) Digest for 09-30-97 (1997) [WebDNA] CMS in WEBDNA (2009) Mac: [ListFiles] bug alert (1997) Banners and sort of random display (1997) WebDNA 6.0 backwards compatible? (2004) Linux vs Jaguar (OSX) (2002) form crasehes server (1997) Help formatting search results w/ table (1997) Re2: AAgghh!! Help, please. SSL strikes again. (1997) Multiple 'Users.db' files not possible (1997) RE: is sku a REQUIRED field on NT (1997)