Christine Eulriet 

Are your termbases all in the same location?

Paul 

Thanks for following up.

To answer your question: all DB were in the same location, one of them also retrieved via a connector.

I spent some time working with Mutliterm opened on the next screen, hoping not to miss any term.  After a few days, this behaviour had disappeared as mysteriously as it came after I had started my computer without having changed any settings or performed any action of any sort. 

I can't link this termbase behaviour to any other change than the update. This is something I also experience from time to time with other applications when an update results in a functionality not working properly for a few days and the issues resolving "on their own".

Best regards,

Christine

Paul 

Thanks for following up.

To answer your question: all DB were in the same location, one of them also retrieved via a connector.

I spent some time working with Mutliterm opened on the next screen, hoping not to miss any term.  After a few days, this behaviour had disappeared as mysteriously as it came after I had started my computer without having changed any settings or performed any action of any sort. 

I can't link this termbase behaviour to any other change than the update. This is something I also experience from time to time with other applications when an update results in a functionality not working properly for a few days and the issues resolving "on their own".

Best regards,

Christine

 Christine Eulriet 

Christine Eulriet said:

This is something I also experience from time to time with other applications when an update results in a functionality not working properly for a few days and the issues resolving "on their own".

Indeed a frustrating experience.  I'd like to come back to the location though... you said they are all in the same location.  Where is that location?  Is it on a OneDrive path or some other network path?  The reason I ask is because this location, by default, store files in the cloud only by default and just leaves a placeholder for you to be able to see that the resource is there.  This means that typically when you select them you normally see an error because the resource isn't really there until it's been downloaded (how long this takes depends on your internet access and the size of the resources); or if you don't see an error you just don't get results.

What you are describing sounds a bit like this so it might be worth checking exactly where this location is, and then if it is on the path to some cloud drive make sure it's set up to always be available locally as well as in the cloud so it's not pulled down on demand... it's just always there.

Just a thought.

Thanks for this hint, I'll keep that in mind (or try at least).
But in the present case, my standard location is a local drive, meaning, if I understood you correctly, that I had now download/synch delay potentially affecting my access to the actual data.
Thanks so muchPaul (pfilkinfor helping out in this specific case and, more generally, for all the support you provides to the community!
Best, 
Christine