Hi Pavel Tsvetkov

I was able to reproduce this, but if you update your Studio as well (CU 3), this will not occur anymore. 

Daniel

Hi Pavel Tsvetkov

I was able to reproduce this, but if you update your Studio as well (CU 3), this will not occur anymore. 

Daniel

I thought Studio had updated itself, but will check that. Thank you! And I discovered I should have a 500 GB D drive after all, just cannot find it ;).

What do you mean with "updated itself"? It has of course updated all program files. But your files are not program files. Imagine, you give Studio your home address in Chicago. So Studio will remember that. When you move to San Francisco, Studio will not know that, unless you tell it - of how do you imagine shall it know about your moving?

Of course I had to tell Studio where my new termbase was. Otherwise it would not be able to find it for the search. However, after the Studio update today and after initialising my D-disk (the supplier had forgotten to add the disk when they prepared it), my termbase is working again as it should and I can also add entries.. NOt sure what exactly did the trick - the D-disk or the update, but it is working. Thank you!

On my end, the problem was solved by repairing both Mutiterm and Studio, and restarting the computer. Now, I still consider this a problem introduced by SDL, as both Multiterm and Studio had been updated when they asked for it, and all steps were followed through, but I still ran into problems

You should either fix your update packages or your update procedure, including instructions on what should follow what, if needed.

Just saying: this is a huge waste of everybody's time, including yours.

Hi  Pavel Tsvetkov

It is sometimes an unavoidable symptom when updating software that something already on the PC setup may trigger some sort of malfunction/incompatibility that means it doesn't work as it should do.

This doesn't only happen with Studio, it happens with other Windows-based software too. The most frequent reason for a software malfunction I find is a large Windows update. That's what Windows Repair was designed to resolve so as far as I'm concerned, it's an unavoidable occurrence from the various software developers' perspective. They cannot know precisely what everyone's individual setup is going to be composed of.

It happens to me with Microsoft Office software too. Office has its own two-level repair facility that it is useful to run now and then.

All the best,

Ali :)

Thank you, Ali!

Thank you!

You're welcome, Pavel Tsvetkov

All the best,

Ali