Dear Nora and the others,

I think I understood whats the problem.

So here is the screenshot. As you can see for the word "elektrohydraulische" in Segment 213 there are 3 matches. Later on in Segment 283 the word "elektrohydraulisch" gets no matches apart from its own translated TU.

BUT...Nora made me doing it (thanks!), so I had a chance to notice that these two words differ in one letter at the end. So my assumption is that somewhere there is an option of showing a match from the same document only if it is EXACTLY the same word or phrase.

This is of course super inconvenient, but at least we are getting closer.:)

So, guys, do you have an idea of which option is responsible for that? I have gone through the Search and Concordance options and didnt find anything that could qualify.

...I just did the concordance search for "Journalisten" - several matches, whereas for "Journalist" - no match! This confirms my assumption.

I will be really thankful for your advises.

We are almost there, just need to identify this root of all evil and kill it:) 

Maria

Do I understand you correctly, you really expect the TM search to show you matches for a single word from a segment with dozens of words? If so, then you unfortunately misunderstand, how a TM works.
A TM will deliver you matches for WHOLE segments (similar by the percentage set in minimum match value to what has been translated in the past). A TM match will however NEVER deliver a match for a single word out of such a segment.
If you need matches for single words, use a Multiterm termbase.

But if you are referring to the search function, so it cannot find "hydraulisch" if you are searching for "hydraulische " (with a trailing space. Try to search for "hydraulisch", then it will find all words with "hydraulisch", including "hydraulische", "hydraulischer" and so on.

Same will apply to the concordance - if you search for a word with a trailing space, this will reduce the amount of what can be found, as the space is also searched for. Try to select words without trailing spaces instead...

Well, I am not searching for the whole segment, dear Jerzy. And you really dont need to suspect me in being a total idiot (thanks again:/). There has always been an option, at least in 2014, of marking a word or a phrase in a source text and then pressing F3-button. By that this word or phrase was placed into a concordance search string and the program looked for all TUs containing this word. Please study the screenshot carefully and you will see that there is only one word in the search string above.
What happens now is that F3 works, the word is being placed into the concordance search but the fuzzy matches are not appearing.

What I need to find out is how to make this search less sensitive. There should be an option. And from my experience, I never needed to do this juggling with endings to find the same rooted words. It is also quite time consuming. I was used to Studio showing me an exact match first and after fuzzy matches, so that I could find what i needed in a split second.

I would really appreciate your help on this issue, if you know, of course

Actually, I think you should be fine with the defaults, which are 70 and 30. If you had the minimum match value set to 100% that would cause only strings that are identical to the search string to be found.

The only thing is, that as Jerzy has suggested, the trailing space in your second search is probably causing the issue and not allowing other partial matches to show, because they don't actually match the string (with the trailing space).

As a suggestion, I see that you're not using a termbase, and for things like these terms, a termbase might be more helpful than Concordance, and it wouldn't require any intervention on your part, the term would be recognized and indicated for you as soon as the segment becomes active. 

Actually, I think you should be fine with the defaults, which are 70 and 30. If you had the minimum match value set to 100% that would cause only strings that are identical to the search string to be found.

The only thing is, that as Jerzy has suggested, the trailing space in your second search is probably causing the issue and not allowing other partial matches to show, because they don't actually match the string (with the trailing space).

As a suggestion, I see that you're not using a termbase, and for things like these terms, a termbase might be more helpful than Concordance, and it wouldn't require any intervention on your part, the term would be recognized and indicated for you as soon as the segment becomes active. 

If you are using Studio 2017 and did not upgrade the TM for fragment matching, so this can also be a reason for your trouble. From my experience TMs without this upgrade do not work properly in Studio 2017.
My recommendation: make a copy of your TM, upgrade this copy and then try to use this one instead of the non-upgraded TM.
And by all means, make use of the UpLift function! You will be astonished by the results. For German into Polish, the UpLift function sometimes builds sentences, which just need to be confirmed, even though the match value shown is around 70%.

BTW, in your screenshot I see, you are updating TWO TMs as you go. From my experience this is not recommendable, as due to the penalty for multiple matches, your hits from TM get penalized, because any fuzzy match, found from both TMs at once is a duplicate of its own. I would just update one TM during the work and then use the "Update main TM" batch at the end to update the other TM. This way you would not get duplicate hits from your TMs.