Hi Esme Knights 

I think you are mixing up Translation Memory settings with Termbase settings.  Click on here and you get taken to the right place:

Then click on the Search Settings here:

Try reducing your minimum match value to less.

Regards

Paul

Unknown said:

The example I will give is "à l’origine de"

This isn't very helpful Esme Knights  Can you tell us what's in your source segment and what's in your termbase that you expect to see?  Then we can play with the settings and hopefully help you.

Regards

Paul

Hi Paul. I've discovered something weird. The problem is with the database. Let me explain. I created a database using Convert Glossary (DB1). I then realised that I hadn't included all of the fields i wanted, so I created another database and gave it a new name (DB2). The problem is that when I first open my file for translation, select DB2, and start to translate, hardly any termbase recognitions show up. However, when I subsequently click on the little termbase icon in the term recognition window and select "use termbase >> DB2", DB1 opens instead. But the weirdest thing is that DB1 contains all of the extra fields that I included in DB2, and DB1 also responds in the desired way, i.e. the term recognition works perfectly. Why is multiterm opening one tb when I ask for another? And how can I fix this? I want to be sure that I am updating the correct tb at all times. I find it very confusing. I hope I haven't confused you as well.

CORRECTION: I am not opening Multiterm, just working in Studio.