Windows 10: Using Excel 2007 workbook in both Windows 7 and Office 365

Hello: I'm actually just looking for confirmation on this. We have a spreadsheet that is built in Excel 2007 version. It opens fine in both the Windows 7 Professional and Office 365 operating systems. However, when a user opens the file on an Office 365 laptop, makes changes and saves them it no longer can be opened on the Windows 7 computer. I believe this is due to the incompatibility of some of the Office 365 features such as data validation with Windows 7. Is this correct?I do think it's time for an upgrade on all the computers, so looking for confirmation that this is in fact the is

:)

 

Excel Taskbar Icon not showing pinned workbooks

The Office 365 Excel Taskbar icon will not show list of pinned workbooks. I have to open Excel and then select from pinned workbooks.

The windows update assistant was used to do an update install, keep programs and files.



Win10 x64 version 1909 (OS build 18262.657)

 

Unable to open office 2007 files in office 365

Had Office 2007 which I have now uninstalled and installed Microsoft 365.

I now am unable to open Word and Excel files created with Office 2007 in Microsoft 365.
I have saved the files again to .docx and .xlsx but still will not open in 365.




Any suggestions?

 

Excel workbook not behaving properly since Windows 10 update

Over 20 years ago, I built a spreadsheet (in Excel 97!) for UK financial advisers. It is still being used by a small number of advisers today.

The workbook has a lot of conditional formatting and a lot of VBA

Over the years, various Microsoft updates have occasionally caused huge issues to the workbook (moving from toolbars to ribbons, introducing SHA512 security, etc). I can forgive this, as a completely new version of Excel or the operating system can be expected
to have some unforeseen side-effects. However, in August, immediately (ie on the next opening of the workbook), after a Windows 10 update, a small but critical bit of the workbook is now failing, which in turn renders the whole of the workbook useless.

There is a separate thread for the fallout from this ( see
this thread )

Depite a lot of work by my VBA programmer, we haven't been able to correct the problem (or even find the bit of VBA that's failing, as the code seems to work fine in Debug mode).

Some bullet points:-

• The workbook worked perfectly well in Office 365 and Win10 up until the mid-August update
• It now doesn't work in Office 365, but still works fine in Office 2007 (I'm setting up some VMs to try other versions of Office - I suspect 2010 and 2013 will be OK, but 2016 will also kill it)
• Even in Office 365, the vast majority of the VBA still works - it is just one very crucial command that fails

I REALLY want to try to resolve this, as the financial advisers that rely on the workbook are desperate to keep using it (and I don't want to have to recommend the use a VM with an old version of Office)

Any help would be greatly appreciated