Hello everyone, my first post here. I realize this is lengthy, but I wanted to provide a full explanation of what I'm experiencing and what fixes I attempted.
Background:
SAP is not my expertise, Excel is, and I have Business Objects Analysis version 1.4.4.2737 with Analysis For Microsoft Excel, working perfectly on my Excel 2010 systems but not on my Excel 2013 systems. I'm reaching out to this forum to ask why that might be.
System specifications are identical for Office 2010 and Office 2013 systems:
• Windows 8.1, 64-bit.
• Office (Excel 2010 and 2013), 32-bit.
• Analysis For Excel, 1.4.4.2737
Question:
What factor(s) would cause the same version of Analysis For Excel to act differently in Office 2013 than it does in Office 2010? Maybe an SP issue? I know a common theme is to match O/S bits with Office bits but Office 2010 at 32 bits never had a problem with Windows 8.1's 64 bits. I'm sure SAP wants all its products to work properly, so this must be fixable, and I'm probably missing something obvious.
Actions:
Example 1
Using Excel 2010, I can run more than one query in the same instance, but in Excel 2013 I cannot open a second query in the same instance.
Example 2
Using Excel 2010, I can run queries in separate instances but in Excel 2013 a second query can get opened; however, functionality is disabled, such as the custom right-click menu, only showing Excel's standard right-click menu.
Example 3
As a work-around to the seemingly necessary new instance creation, I wrote an Excel VBA add-in to programmatically force a new, separate instance when triggered by the attempt to open a second query or second workbook in the active instance. My add-in does create a new instance as it should while in the Analysis For Excel environment, but the Analysis tab does not appear on the Ribbon for the workbook in that new Instance. I was hoping AFE would automatically load with the programmatic creation of a new Excel instance from an existing AFE instance, but it does not.
Example 4
Even with no Excel add-ins loaded, a message appears for Exception 0X800A00A8 while opening Analysis For Excel in Office 2013.
Example 5
I can set Excel's MergeInstances property to False, to bypass Excel 2013's default detection logic that knows when an additional, new instance of Excel is starting up, and merges that workbook (and new Excel instance) into the instance of Excel that’s already running. That bypass does work, but it does not solve the larger issue of Excel 2013's difficulty with Analysis For Excel that works great in 2010.
Anyone ever deal with this (or hear about someone who did), and how it was fixed?
Thanks so much for any ideas or direction you may have.
Tom