How to filter portal using whole words?

[K1200]

I have a simple situation and thought there was a simple portal filtering solution.

 

I have a text field that contains phrases:

 

"Newly Minted in New Hampshire"

"New Ways to Run a Railroad"

"An Old Story Told Anew"

"Newfound Methods"

 

When I set New as the filter keyword, it displays all four records.  But what I'm trying to display are the first two. 

 

My portal filter is set as PatternCount (Table::Field ; Master::Keyword ) > 0

... which I understand is looking to locate the text anywhere in the string.  But this is where I thought there was a technique that could be applied.  I've tried using apostrophes around the keyword and a equal sign prefix, but filtering just includes them in what it tries to match.  It doesn't interpret them as filter rules.

 

Any suggestions of what might work?  (BTW, I'm operating with a separation model database and can't add anything to the table that holds the phrases.)

 

Thanks in advance for any help.

[Raybaudi]

This ?

 

Left ( Table::Field ; Lenght ( Master::Keyword ) ) = Master::Keyword

[K1200]

Thanks for your response.

 

But unless I've misunderstood your suggestion, it displays all except "An Old Story Told Anew".

Plus, it seems to only look at the first word of a phrase.  Is that correct?

[mr_vodka]

Perhaps you are looking for something like:

 

http://hbase.net/2010/07/29/type-ahead-style-searching-through%C2%A0portals/

[Raybaudi]

Then you could try this other one:

ValueCount ( FilterValues ( Substitute ( Table::Field ; " " ; ¶ ) ; Master::Keyword ) )

but you'll have to filter all punctuations.

[K1200]

That's the solution I was hoping to find.  Simple.  And versatile.  I can certainly handle the punctuation aspects of it.  In fact, there might be other uses that can benefit from special characters that I can find and exchange.

 

Thanks very much!!!

 

 

 

@MrVodka:  "In the Portal Record create a calculated Search Field".  A reasonable method, certainly with advantages ... but I can't add a field.  Thanks, for the suggestion.