Compatibility Multiterm 2017 with Multiterm 2015

We recently discovered that termbases created with Multiterm 2015 couldn't be opened with Multiterm 2017. This had as consequence that terms in a project were not recognised. Is there a solution so that term recognition would be assured not only in the project created by the PM but also on the translator's computer, whatever Studio version (s)he uses (starting from 2011)

Parents Reply Children
No Data