Unfortunately, something is really wrong and this is beginning to be a very annoying issue! Sometimes, I am able to do as Sorin said, among other further checks and cleanups, but everytime I restart Studio, I have to do all of this again and sometimes it works and other times I get the same error message! I guess RWS has to arrange with Microsoft for this nightmare to be over! 

Unfortunately, something is really wrong and this is beginning to be a very annoying issue! Sometimes, I am able to do as Sorin said, among other further checks and cleanups, but everytime I restart Studio, I have to do all of this again and sometimes it works and other times I get the same error message! I guess RWS has to arrange with Microsoft for this nightmare to be over! 

It is very annoying. I believe it's beacuse the Studio developers test only in a vanilla environment (if they actually test at all), i.e. with no macros in Word.

André Stryger 

André Stryger said:

I believe it's beacuse the Studio developers test only in a vanilla environment (if they actually test at all), i.e. with no macros in Word.

There is no need for comments like that.  Please be constructive if you have something you'd like to add to the discussion that will be helpful.  In this case it would perhaps be useful if you told us what macros you think we should include?  It might also be useful if you told us what other software we should include. After all, if we are not going to test in a vanilla environment what single environment containing the things you believe everyone uses should we have?  Or maybe you can suggest a range of environments that you think we should test against... in addition to the different language operating systems we already test against?

Currently if you want to use Trados Studio and the Word spell check enabled inside it, you are not allowed to have any macros in Word. That's not acceptable.

I would suggest you invite more real users to test in their environment. Regarding macros in this case it doesn't matter which macro. Having any macro is the problem since apparently Studio copies the Word template file into a temporary folder and Windows (or Word) and that creates havoc with Word.

Correction: Having any macro is the problem since apparently Studio copies the Word template file into a temporary folder and that creates havoc with Word.

By the way, as a proficient proofreader I must say that the review mode in Studio is utterly insufficient. I would like to contribute to a proper understanding of what this task really involves. I would like to discuss this with you outside of this forum if you're interested. :-)

André Stryger 

André Stryger said:

I would like to discuss this with you outside of this forum if you're interested. :-)

I would far prefer you to create a new thread specifically for this and we can discuss it here.  I think opening a discussion like this to all our users would be far more valuable and also carry more weight.  We could then take any concrete suggestions from the discussions and provide them as ideas in the ideas site so the product manager could consider them for inclusion in the product.

Has anything been done with the macro issue?

All of a sudden this problem has cropped up for me with Word (Office 365) and Studio 2024). No updates in Office since it last worked and now or indeed to Studio. So this is weird. And none of the solutions mentioned here work.