ha ha i wasn't disputing that it wasn't doing what it is supposed to, but doesn't mean it's good or overly useful especially if your users can't spell ;) lol
If your pickin' up what I'm layin' down...
If your pickin' up what I'm layin' down...
--- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
>
> That "where part desc contains" search uses the SQL server full text search, which assumes its searching paragraphs of English text. Entire words only, synonyms checked, stop words apply... unfortunately, not the best tool for a part description where abbreviations etc are common. So to the OP: its technically working, just not doing what you want J
>
>
>
> My workaround was building an advanced search, with some customizations that lets the user enter just "cott" but internally searches for MATCHES "*cott*". (MATCHES doesn't use the full text index).
>
>
>
> Thanks,
>
> Brian.
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jgiese1988
> Sent: Wednesday, October 31, 2012 8:54 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Part search doesn't work with "Where Part Description Contains"
>
>
>
>
>
> I built a custom instant search with a BO reader that performs a LIKE statement. Works 100% of the time. Part Search "Where Part Desc Contains" works for crap for us too. It seems you have to type a full word to get it to recognize it, and you cannot use asterisk characters in the string. For example "cott" will return no parts "cottage" will return only some of the parts that contain that string, the full real string in the description is "*cottage*" which seems to return nothing. Who knows?
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , Tony Karugu <tonykarugu@> wrote:
> >
> > Hi guys,
> >
> > we have a similar issue with description search, i still have a call open to Epicor Support on the same. We are using Epicor9.05.700C ProgressDB. Its on testing meant to go live in January. I tried re-indexing using proutil commands, the logs show that all are active. We also had uploaded data before using DMT before i could activate the indexing which in essence when using progress they are active.
> > As for Epicor9.05.700C SQLdb and E9 prior versions one needs to activate Full Text Search and run the indexing scripts to activate description search.
> >
> > Regards
> >
> > Anthony
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: "james.moore@" <james.moore@>
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Sent: Tuesday, October 30, 2012 6:23 PM
> > Subject: RE: [Vantage] Part search doesn't work with "Where Part Description Contains"
> >
> >
> > Â
> > We had the same issue in 9.04 and we had to re-index the database.
> > Sounds worse than it actually is.
> > That fixed the problem for us.
> >
> > In EpicWeb Answerbooks:
> >
> > See 13486MPS for SQL.
> > See 12207MPS for Progress.
> >
> > Jim Moore
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On Behalf Of kayd.indaco
> > Sent: Tuesday, October 30, 2012 10:07 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Part search doesn't work with "Where Part Description Contains"
> >
> > We are testing 9.05.700C and cannot get Part Search to work. Parts were first loaded using DMT and we couldn't get any results when searching for a particular word in the part description.
> >
> > We then added a part manually (without using DMT). Still nothing shows up after entering a word in the section "Where Part Description Contains".
> >
> > A list of parts appears if we use "Search" only, but that isn't what we're looking for. Has anyone else had this problem or does anyone know a resolution?
> >
> > Thanks in advance for any help.
> >
> > Kay Doolin
> > Indaco Metals LLC
> > 405.273.9200
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>