Talia

For termbases, this should still work because Studio only checks that the base languages match. This means that you can work with an EN-UK termbase and EN-US in your project. The culprit must be somewhere else.

Can you do a termbase search when you switch to the tab "Termbase Search" and search for an existing entry in your termbase?

About your question on how to change the languages in your Termbase: you would need to export you termbase, create a new termbase  using the same definition, change the languages in the wizard and import the exported content file into the new termbase.

Usually, best practice is to only use base languages in termbases (i.e. English, Spanish, etc.) and not variants of languages. By default, Multiterm does actually not show the language variants unless you check the corresponding checkbox.

Walter

Unknown said:

For termbases, this should still work because Studio only checks that the base languages match. This means that you can work with an EN-UK termbase and EN-US in your project.

I'd just add one thing to this Walter... sometimes if you don't have this set correctly then when you add new terms the target language doesn't get populated.  But you're right, it probably should still show some recognition.  Best to work with base languages as you said.