Page 1 of 1

Enhanced Search in Sage Line 50 V15

Posted: 23 Jun 2009, 08:00
by coolguysvenster
Hey,

Is there any way, shape or form to enhance the way sage searches work or impliment something into sage to enhance search functions?

I have far too many products to use a phonetic product code system where for example i can identify products to certain product codes so i have no choice but to use barcodes and single one off product codes etc. However sage only permits me to search for the exact word of phrase in the details section for example of the products record and does not allow me to enter just a keyword and then bring up a list of all product records that have that word in them.

At the moment i link the sage database into a rarther jazzy excel table i made with like a global search but when you are processing orders all day via telephone for example where you don't have product codes it is a real nightmare having to keep flicking back and forth to find the product, then go enter it into sage with Qty's etc and then go back to the excel spreadsheet and so on and so on.

Any ideas or better ways to enhance the peramiters/criterias for sage searches. Is there anyway to add a "contains" to the "is Equal to" and "is not Equal to" criterias?

Cheers, Any help or suggestions would be much appreciated.

Steve

Re: Enhanced Search in Sage Line 50 V15

Posted: 23 Jun 2009, 15:14
by brucedenney
Yuo can use wildcards to do that

eg Description Is equal to *dry*
will find where dry is in the description somewhere

Re: Enhanced Search in Sage Line 50 V15

Posted: 29 Jun 2009, 14:18
by coolguysvenster
Thanks Bruce,

that is somewhat useful and deffinately worth knowing, but only seems to work with numerics and not words.

If i use Description is equal to *dry* nothing happens for example no results are found.
If i use Description is equal to *16* then it brings up all the "16"'s perfectly.

Is there another wildcard at all or way of phrasing it?

Steve

Re: Enhanced Search in Sage Line 50 V15

Posted: 30 Jun 2009, 08:45
by brucedenney
It works for me, it is case sensitive...