# How to eliminate the false reports as could as possible when composing the Source expression?

**URL:** <https://forum.xbench.net/t/how-to-eliminate-the-false-reports-as-could-as-possible-when-composing-the-source-expression/693>\
**Category:** Technical Support\
**Created:** [November 18, 2020, 8:47am UTC](https://forum.xbench.net/t/how-to-eliminate-the-false-reports-as-could-as-possible-when-composing-the-source-expression/693 "2020-11-18T08:47:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![x69toki](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/x69toki/32/249_2.png) [@x69toki](https://forum.xbench.net/u/x69toki)\
**Post date:** [November 18, 2020, 8:47am UTC](https://forum.xbench.net/t/how-to-eliminate-the-false-reports-as-could-as-possible-when-composing-the-source-expression/693/1 "2020-11-18T08:47:33Z")

</div>

How to eliminate the false reports as could as possible when composing the Source expression?

Dear Sirs,

I am composing a source expression in order to search for the term: “February” or “Feb”.

* * *

It looks like this:

`Source: (February|FEB|Feb|Feb\.)`

`Power Search: on`  
`Case-sensitive: off`

* * *

However, I found that such expression will fetch the words that contain any letters referring to “feb” in the source sentences.

 ![圖片 001](https://canada1.discourse-cdn.com/flex035/uploads/xbench/original/1X/068d73b6f77da63f9e520f34f77e33dd309388db.png)

Is it possible to eliminate such false positive?

Thanks in advance. 😃 👍

---

<div class="post-metadata">

**Author:** ![Manuel](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/manuel/32/163_2.png) [@Manuel](https://forum.xbench.net/u/Manuel)\
**Post date:** [November 18, 2020, 9:08am UTC](https://forum.xbench.net/t/how-to-eliminate-the-false-reports-as-could-as-possible-when-composing-the-source-expression/693/2 "2020-11-18T09:08:58Z")

</div>

Hi [x69toki](https://forum.xbench.net/u/x69toki),

Yes, it is. Just toggle `Match Whole Word` case on for `Source` search on the check ;).

Kind regards,

P. S.: BTW, if `Case Sensitive` case is off, it is meaningless to include both “`FEB`” and “`Feb`” on your search. Probably, just toggling `Case Sensitive` on would be enough for your purposes, but if you want to avoid the potential false positives from “Febrile”, “Febricula” or the like, toggle `Match Whole Word` on as well.

---

<div class="post-metadata">

**Author:** ![omartin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/omartin/32/82_2.png) [@omartin](https://forum.xbench.net/u/omartin)\
**Post date:** [November 18, 2020, 9:22am UTC](https://forum.xbench.net/t/how-to-eliminate-the-false-reports-as-could-as-possible-when-composing-the-source-expression/693/3 "2020-11-18T09:22:52Z")

</div>

As Manuel states, this is reported because the `Match Whole Word` checkbox is not enabled for the source term. Indeed, you should enable `Case-sensitive` since it will find examples such as fEB or fEb.

---

<div class="post-metadata">

**Author:** ![x69toki](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.xbench.net/x69toki/32/249_2.png) [@x69toki](https://forum.xbench.net/u/x69toki)\
**Post date:** [November 19, 2020, 4:30am UTC](https://forum.xbench.net/t/how-to-eliminate-the-false-reports-as-could-as-possible-when-composing-the-source-expression/693/4 "2020-11-19T04:30:09Z")

</div>

Hi Manuel and omartin,

Thanks a million!!!

I will give it a try today. 😃