Pavel Tsvetkov

I tried to test this, added 20 terms, took a little while to open the termbase management window and for a second I thought you were right, but then it opened.  I closed MultiTerm, opened it up and the layout was fine, so I added another 11 terms and tried again, same thing... no problem.

I'm wondering what's wrong with your layout as well?  You are just showing the "Full layout" as opposed to the default you showed at the start.

Whilst I can't reproduce your error I can't say I'm completely surprised as MultiTerm can have memory issues, especially once the termbase starts to get large.  How large is your termbase?

Hi Paul,

1.Here is my termbase:

2. Another thing worth trying on your end: try adding a new term a bit too soon. By that I mean that you should copy the term from a source document, click on the button to add a new term in Multiterm (opened as a stand-alone tool) and before the new empty term form is fully opened, paste. This breaks Multiterm most of the time in such a way that it has to be forcefully closed and re-opened. In the process, your termbase may get corrupted.

Best regards,

Hi Paul,

As of late, Multiterm (when used as a stand-alone tool) seems to have been acting a little better with regard to breaking down while adding new terms, but adding a new term too soon (before the new term fields are fully open) will break Multiterm almost 100% of the time. Then, every now and then, I will come across existing but somehow faulty entries:

This is quite interesting, as the term is listed as existing but when I click on it an error message pops up. When I export the termbase to an Excel file and look for this specific entry, it is there and has a translation, all seems to be in order. However, I have to delete it from the Excel file and then create a new termbase and import the Excel file to make sure that I have a 100% working termbase.

All this takes a long time...

Best regards,

P.

Pavel Tsvetkov

It might be worth turning off your Lookahead function if yu have not done this already as it might be messing with this.