<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Ken,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The way I suggested is more accurately defined as a full-text and a phrase search. After thinking about it a bit more, I think a whole word search will do so I’ll implement that first and see if that will satisfy them. If it doesn’t,
it won’t take much more to implement my original phrase search, not to mention the savings in performance if the word searching suffices.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyone have a snippet that can breakdown a long field into separate words using the space as a delimiter. This also produces way less generated GL_tags records to create by at least a magnitude of 10-20 to 1. Its worth a first try.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Stanley<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> Ken Cole <ken.m.cole@gmail.com> <br>
<b>Sent:</b> Monday, October 21, 2019 7:54 PM<br>
<b>To:</b> Stan-Lyn, Stanley Barnett <stanley@stanlyn.com><br>
<b>Subject:</b> GL Tags<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Stanley,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have started a new thread for our discussion as the existing discussion was being muddied by the other contributors.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I totally understand what you are saying with the 3 char, 4 char words.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don’t think it is needed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If we do the lookup with a “greater than” lookup and use the drop commands in lookup processing we only need the whole words.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This is what I suggest:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1. I agree with your proposal to delete existing records for a GL code and re-parse each time.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">2. I also agree on removing the “- “ when parsing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">3. We only parse our whole words.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">4. I agree with Nancy et al that neither contains or fuzzy search will work adequately as they will return too many false positives.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">5. The user can enter as few or as many characters as they want then press enter to fire off the search.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">6.. We use a lookup greater than match and use drop commands in the lookup processing to “drop all before” and “drop all after” to constrain the lookup to only words that start with the characters the user typed in.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">7. When the user selects an entry in the browse popup it sets the associated GL_code.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am sure this will do what you are looking for.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Ken<o:p></o:p></p>
</div>
</div>
</body>
</html>