"Probability score": 0.8

"Question improvement suggestion": Please provide more information about any error messages you might be receiving, and any troubleshooting steps you have already taken. Also, it would be helpful to know if there have been any recent changes to your system or software.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Jennifer,

It seems like you're having trouble with MultiTerm 2019 not recognizing termbases created in MultiTerm 2015. Here are some steps you can try:

Step 1: Ensure that your Windows 10 is up-to-date. You can do this by typing "Check for updates" in the Windows Search bar and following the prompts to install any available updates. Restart your computer after the updates are installed.

Step 2: Try repairing your Trados Studio and MultiTerm installations from the Control Panel. You can find instructions on how to do this in the articles "Repairing your installation of Trados Studio" and "Repairing your installation of MultiTerm Desktop".

Step 3: Check the folder name or file path where the termbase is saved. If it contains any special characters, try changing it to something simpler.

Step 4: If the issue persists, you might need to convert your MultiTerm 2015 termbases to a newer format that MultiTerm 2019 can recognize. You can do this using the "Upgrade Termbases" function in MultiTerm 2019.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Jennifer, your termbases have the extension .sdltb and those are the only files you need to be concerned about and which you can open with ANY version of MultiTerm. For instance, if you created a termbase with MultiTerm 2015, you certainly can open it with MultiTem 2019, 2021, 2022, 2024, etc. It's the same format.

Those .mdf and .mtf files are just auxiliary or support files that enhance the functionality of the termbase and have nothing to do with the actual content of the termbase.

Jennifer Gray 

Looks like a duplicate question to this one that we also answered:

 Multiterm 2019 does not recognise termbases created with Multiterm 2015 

It would be useful to know if anything helped so we can make the post closed before anyone spends their valuable time trying to help!