Strange behaviour after OS reinstall

[dobre.dani]

Hi,

I have recently purchased an SSD, then later I got a second laptop. I now have 3 OS installations, I'll call these OS_OLD, OS1 and OS2.
OS_OLD was running for 2.5 years with Excel 2003, 2007 and 2013. Excel 2013 was installed quite recently and my main version was 2007.
OS1 installed when I got my SSD and has Excel 2003, 2007 and 2013 all installed the same day.
OS2 only has Excel 2013.

My problem:
I have code running perfectly fine on OS_OLD but on OS1 is missing "Microsoft Windows Common Controls 6.0" reference. Even after browsing to the mscomctl.ocx file, the reference still shows up as missing next time I am running the macro. Strange enough, on OS2 I get a missing reference to "Microsoft Office Document Imaging 11.0 Type Library".
Since MODI is no use in this project, I have simply unchecked and it works fine. However, that was not the case with mscomctl.

Further on with the problems, on OS1 if I open workbooks in Excel 2007 I get "Excel found unreadable content" although the same file opens just fine in 2013.

One project that was started on OS_OLD (Excel 2007), was continued on OS1. So previous versions of the workbook were fine, but as soon as I made changes to the code and delivered to my client, he experienced same issue with "unreadable content" in 2007. My client confirmed that the file had no issues when opened in Excel 2010.


The solution I am after:
Fix my Excel 2013 installation on OS2 so that code delivered to previous versions (2007,2010) won't get unreadable content or any missing references.

Can you help me understand the issue and/or solve my problem?

Many thanks,
Dani

[dobre.dani]

Me again.

It crossed my mind that the architecture difference between the OS installations could be the culprit. OS_OLD is 32-bit while OS1 and OS2 are 64-bit.
With this in mind, I was able to find similar issues posted on the net, so I have pretty much figured the missing references:
- MODI is only available to 2003/2007, therefore it is missing from OS2 where I only installed 2013.
- mscomctl.ocx was probably referenced to system32 when it should have been to WOW64 folder. I am unsure about this part and mostly I am buffled that in 2.5 years not one client reported missing references from the macros I delivered, and I am pretty sure some of them had 64-bit OS.

The unreadable content is still a mistery. A macro enabled workbook that opens fine in 2013 does not open in 2007 (on OS1) even though the workbook was originally created in Excel 2007 (OS_OLD).

I appreciate any thoughts on this.