Re: Search Combining Problem
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 57984
interpreted = N
texte = Still having the same problem. If you would like to see the results of the search you can view them at this url http://www.mrminocqua.com/mlschainsearchresults-test.html Here is the current search code which is still finding the word "Big" in any lake name that contains it as the first word of the Lake Name. [search db=^MLSData/mls.db&REMARKS1word=ww&REMARKS1wbrk=,&REMARKS1fbrk=,&wsREMARKS1d atarq=LAKE/RIVER: Big,LAKE/RIVER: Mamie,LAKE/RIVER: West Bay&LISTPRICEtype=num&LISTPRICEsort=1&max=15] We are using Webcat 4.51, so I'm not sure if the fbrk option is a valid function in this version. Jesse ----- Original Message ----- From: "Brian Fries"
To: "WebDNA Talk" Sent: Monday, May 24, 2004 1:40 PM Subject: Re: Search Combining Problem > 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/ > ------------------------------------------------------------- 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:
Still having the same problem. If you would like to see the results of the search you can view them at this url http://www.mrminocqua.com/mlschainsearchresults-test.html Here is the current search code which is still finding the word "Big" in any lake name that contains it as the first word of the Lake Name. [search db=^MLSData/mls.db&REMARKS1word=ww&REMARKS1wbrk=,&REMARKS1fbrk=,&wsREMARKS1d atarq=LAKE/RIVER: Big,LAKE/RIVER: Mamie,LAKE/RIVER: West Bay&LISTPRICEtype=num&LISTPRICEsort=1&max=15] We are using Webcat 4.51, so I'm not sure if the fbrk option is a valid function in this version. Jesse ----- Original Message ----- From: "Brian Fries" To: "WebDNA Talk" Sent: Monday, May 24, 2004 1:40 PM Subject: Re: Search Combining Problem > 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/ > ------------------------------------------------------------- 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/
"Jesse Crofoot"
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:
Emailer (1997)
More questions about serial number dishing (1997)
Instructions for Digest (1997)
can webcat determine an image's pixel dimensions? (2000)
Grouping fields problem (1998)
Re:multiple digests, please stop (1997)
different browser, different result (2000)
More on IE5 (2000)
Payment calculator ?? (2000)
[OT] Robust order processing (2003)
Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997)
RE: Help name our technology! (1997)
WC2.0 Memory Requirements (1997)
sorting and summarizing (1998)
MacAuthorize order data fields WAS:How To question... (1997)
re: keep W* in front applescript? (try Cron) (1998)
WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997)
Exclude by date - multiple (1997)
iTools and 3.0.8 (2000)
WebCat2 Append problem (B14Macacgi) (1997)