Problems openning files creeated in xxcel 2010 2010 with Xcel 3012

[Rev. Michael L. Burns]

For several years now I have been using Office 2010 and have created a number of monthly XL documents using an Ad-in called XLTools to allow me to select a date from a calendar in the date column of each spreadsheet. This has worked perfectly.

Two days ago, I upgraded to Office 365 Version 2016. Every Excel file created in Office 2010 open in Protective mode in Excel 2016. I can't seem to correct this. Any ideas?

I have added the version of XLTools that is supposed to work with 2007, 2010, 2013 and 2016. No help. But I can create a new Excel 2016 with XLTools and it works fine.

Compatibility between Word 2010 and 2016 work with no apparent problem so I assume it's XLTools related.

Michael

 

[Trouble]

Do you see an option button that says "Enable editing"?

 

[Rev. Michael L. Burns]

No but I have decided that it is not XLTools related although XLTools is present in the failing files. If I create a file from scratch with XLTools present, it works fine when opening it in Excel 2016. When I select View/Macros, some of the troublesome files show macros while others do not.

I have noted one common thread in all the files that are opened with Protective Mode on though. Each file was built upon an example someone sent me several years ago. Each file is made up of several Sheets. The first sheets basically acts as a check register. the second sheet is used for instructions on how to use the file and files the dropdown on sheet one with who I pay my bills to, etc., it must be a macro or VBA code. Either way, it appears to be hidden.

When I open a file and get the Protective Mode message, my first attempt to save it tells me that Protective Mode files cannot be saved and then offers me the option to Save it anyway. If I do that and then Close the file and then reopen it I get a Security Warning advising me that Macros have been disabled although View/Macros may or may not indicate any. If I enable the macros and try to save it again I get a further message that the file is saved on a network location. That's to be expected since I usually save all my files to OneDrive so as to access it from anywhere. But I never saw that in Office 2010. At any rate, I saved one of the Protective Mode documents to Documents on my Desktop, opened it from there and got the Protective Mode warning, Saved it anyway, closed and reopened it, got the Macros disabled message. Enabled it, saved it, closed and reopened it. Opens perfectly now from my Desktop but loose the ability to access from anywhere. Copying back to OneDrive opens in Protective Mode, saving it anyway indicates macro disabled again, enabling them, resaving and then ignoring the network message allow it to work properly from then on. Must be an easier way that won't harm my system. All of this has been using Excel 2016.

Michael

 

[Rev. Michael L. Burns]

I think I may have further shot myself in the foot. To eliminate any possibility of incompatibility, I uninstalled Office 2010 completely, all Office Mobile applications and left only Office 365 Version 2016 on my system. Opening file from Word 2016, Excel 2016 and Access 2016 open ok from within the programs themselves but now File Manager will not and asks me How I Want to Open the File but does not offer any Office 2016 applications as an option.

I've tried following several examples for setting default but I keep falling victim to "Operator Head Space", that emptiness between the ears. Can someone give me a clear step-by=step how to associate my Office 2016 apps as defaults?

Also, after I installed Office 2016, if I open the Start Menu and select All Apps and scroll down I can see the normal icons for each of the applications. However, if, say for instance I pen Excel 2016 to the Start Menu, I get only a colored box with the application name but no icon. If I pen the same application to the task bar I get the expected icon. All other programs show the icon when penned to Start but not Office 2016 apps. This is the only application installed since updating Windows 10 last week.

Michael