Unknown said:

Trados 2007 is now a very outdated piece of software (over a decade old) which simply is not compatible with newer (2010 onwards)MS office versions.
There are I think only two options available - downgrade your Office version if you wish to continue using Trados 2007 or switch to Studio 2019.

I'm afraid this is pretty incorrect information.
I was successfully using Trados 2007 with Office 2010 just a few months ago (when I was still active in localization engineering).
Trados 2007 has always worked with Office 2010 and there is no reason why it would not keep working...

Can you back your claims with some serious proofs and technical explanations?

I'm afraid that it's rather about Office bitness - it's notoriously known that 64-bit Office is NOT compatible with vast majority of 3rd party addins and/or macros...
And the Trados add-in for Word (which is what we are probably talking about, since Krzystof mentions the Trados tab on ribbon) extensively works with Word VBA macros... i.e. requires 32-bit Office.

Unknown said:

Trados 2007 is now a very outdated piece of software (over a decade old) which simply is not compatible with newer (2010 onwards)MS office versions.
There are I think only two options available - downgrade your Office version if you wish to continue using Trados 2007 or switch to Studio 2019.

I'm afraid this is pretty incorrect information.
I was successfully using Trados 2007 with Office 2010 just a few months ago (when I was still active in localization engineering).
Trados 2007 has always worked with Office 2010 and there is no reason why it would not keep working...

Can you back your claims with some serious proofs and technical explanations?

I'm afraid that it's rather about Office bitness - it's notoriously known that 64-bit Office is NOT compatible with vast majority of 3rd party addins and/or macros...
And the Trados add-in for Word (which is what we are probably talking about, since Krzystof mentions the Trados tab on ribbon) extensively works with Word VBA macros... i.e. requires 32-bit Office.

Last time I installed Office it wanted to default to the 64-bit version, so I had to follow a few links to find the 32-bit version to install -- yes, I had been caught by this problem in the past and was playing it safe by avoiding the 64-bit version  :-)

(If I remember correctly, 32-bit Office used to be the default when installing on 64-bit systems.)

Unknown said:

Last time I installed Office it wanted to default to the 64-bit version

Yep, I believe THIS is precisely the thing leading people with not enough experience to completely wrong conclusions.

On the other hand, such behavior is quite strange because Microsoft itself clearly states that one should go for 32-bit Office unless one has one of the serious reasons to opt for 64-bit.

Unknown said:

I'm afraid this is pretty incorrect information.
I was successfully using Trados 2007 with Office 2010 just a few months ago (when I was still active in localization engineering).
Trados 2007 has always worked with Office 2010 and there is no reason why it would not keep working...

Can you back your claims with some serious proofs and technical explanations?

I think Steve was providing a correct answer even though I know some people still manage to make it work.  The issues, as you are well aware would be these and this is what he was referrings to:

1. Most people go with default Offfice installs and use 64-bit - Trados 2007 won't like this

2. Trados 2007 has not been tested by SDL on any version of windows for nearly a decade, and won't be either

I use Office 2016 32-bit, still work with Workbench occasionally but I haven't been able to make it work in Word correctly for a long time.  Having said that, I haven't tried too hard either... my eyes tend to glaze over as soon as I start to see template problems and any of the other longstanding Trados issues.

I guess the problem Steve, and many newer people (less than a decade of experience!) to the technology have is that they won't be able to help with the old Trados issues anyway.  Perhaps next time he can just change his answer a little so it just says we don't support it anymore, perhaps some of our veteran users will be able to offer some advice!