Same here... When I change the capitalization of an entry the TermBase asks me if I want to merge the entries. Then I get a "Script on this page" error and maybe this is what corrupted my TermBase such that in most segments no or only some terms show up. I will now try (to find out how to) reorganize my termbase and see if it fixes the issue. Maybe this can be a hint for the TRADOS team to resolve the reason for this symptom.

Same here... When I change the capitalization of an entry the TermBase asks me if I want to merge the entries. Then I get a "Script on this page" error and maybe this is what corrupted my TermBase such that in most segments no or only some terms show up. I will now try (to find out how to) reorganize my termbase and see if it fixes the issue. Maybe this can be a hint for the TRADOS team to resolve the reason for this symptom.

On a quick look I cannot find how to do this in Studio - Google searches suggest I will need Multiterm to do reorganize my TermBase. So I have to buy Multiterm for SDL TRADOS STUDIO to work properly? That's one way to make money ... :)

Edit:

Quick anything is never such a good idea. :) Thank you Paul Filkin from SDL for the hint that Multiterm is free! :) I was working under time pressure and my termbase was failing on me. But I do think it is a good idea for the SDL developer team to look at the issue that changing capitalization disrupts termbases. I have to quit and restart SDL TRADOS STUDIO after such a "script on this page .... do you want to continue running this page Yes/No"-error in order for the termbase lookup to react at all and after the restart it is disrupted.

Unknown said:

Same here... When I change the capitalization of an entry the TermBase asks me if I want to merge the entries. Then I get a "Script on this page" error and maybe this is what corrupted my TermBase such that in most segments no or only some terms show up. I will now try (to find out how to) reorganize my termbase and see if it fixes the issue. Maybe this can be a hint for the TRADOS team to resolve the reason for this symptom.

This is a different issue to the one reported above.  Are you running the weblookup plugin by any chance?

Unknown said:

This was faster than having to download and install Multiterm but I guess it does not ensure proper handling of all and every eventuality of some TermBases. Mine worked fine but I am keeping a backup of my old one just in case.

You should probably install MultiTerm anyway so you have it handy when you need it.  Easy to find, just go to your account and to the same place you found the download for Studio.  Multiterm is there too.