Term recognition stops working in trados 2017

Hi everybody, I hope somebody can help me with this issue. 

In the middle of a project, Trados 2017 suddenly stops recognizing terms and the term recognition window looks empty (even if the termbase contains many of the terms in the source text).

If I shut down trados then the problem disappears and it works fine for another half an hour.

As you can see from the attached screenshot, the term "emphysema" is in the dictionary but trados doesn't recognize it.

(by the way, I am using the latest version of multiterm and trados)

Can you help  me?
Thank you! 

Parents
  • Hi, I had this problem too.

    My project folder with 2 termbases gets syncronized with Google Drive and this could be a problem.

    I add words continously in the primary termbase when translating, but this termbase stops to show words in the Term Recognition window. If I use the Termbase Search to find the words. Trados finds the words in the termbase. The second termbase keeps to show words in the Term Recognition window.

    I tried to reorganise the primary termbase, but Multiterm crashes before finishing the reorganisation. I have tried several times. Then I put the primary termbase in a folder on the desktop and then the reorganisation was successful.

    I copied back the primary termbase in the project folder in the folder which gets syncronized with Google Drive. Now the Term Recognition functions again. And until now it still works even if I have added more terms to the primary termbase.

    So the problem can´t be the fact that I use syncronization with Google Drive, but I don´t think it was a coincidence that Multiterm was crashing all the time, when I tried to reorganise the termbase when it was in the folder which gets syncronized with Google Drive.

    Best regards
    Thomas
  • Hi again, more feedback in this matter: After working a while a recently added word again did not appear in the Term Recognition window. Other words from the termbase are shown. I once again did a reorganisation - this time I could do the reorganisation in the folder which gets syncronized with Google Drive - and now the word is shown in the Term Recognition window. I don´t know what the problem is, but to reorganize the termbase so frequently is not really a solution.
  • I'm having the same problem and my termbase is in a local folder. Judging from a few other threads on similar issues, this seems to be a known problem that SDL is working on, is that right? Any news?
  • This problem has existed for years and years and years, and there does not seem to be any way to fix it, apart from if SDL decide to change the underlying database format (Access/Jet). I have NEVER gotten Studio (2014, 2015, 2019) to reliably recognise terms I know are in my termbase, no matter how small or new or correct the termbase, no matter whether I reinstall Studio from scratch, reorganise the termbase, Repair the installation ,etc. None of this works because the problem is systemic. That is, the terminology recognition system just does not really work very well in Studio.

    They recently moved the TM database system to SQLite (which was a great idea), so all we can do is pray they decide to finally ditch the crap underlying database engine termbases / term recognition relies on. Until then, no matter what you do, you will never really know if a term is already in your termbase.

    Michael

  • Hmm, by the way, out of frustration, I have been testing all of the different terminology systems offered in Studio 2019, so I tried SDL Language Cloud (Beta) next. And guess what: exact same problem. More than half of what I enter in my termbase, or is already in it, is not recognised. Very sad.

    By the way, term recognition works flawlessly in CafeTran, memoQ, Déjà Vu, and many other CAT tools, so it isn't rocket science.
Reply Children