I made a excel spreadsheet using office 2013 and it works fine. But when i try to open it in office 2010 it will crash when retrieving data.
My configuration: office 2013 - x64
Client: office 2010 - x32
data source: odbc
I have no clue what is wrong,
what have i tried:
if i do click on edit query and run the query it runs but as soon as i hit the button to take the data back to office it will just crash.
Have you tried installing powerpivot for office 2010?
This may give you a cleaner and more powerful solution, adaptable in both versions of Excel
Related
I'm trying to mess around with some dashboard/BI tools since Power BI is no longer free and stumbled upon Power Query/Power Pivot as a potential solution.
I installed Power Query (x32) and am since unable to load excel 2010 when the add-in is enabled. When I disable the add-in Excel opens with no issues. When I re-enable the add-in Excel hangs for a brief moment and then crashes.
I'm running on a 64-bit Windows 7 machine with a 32 bit Excel 2010 installation.
Any thoughts as to what could be going on here?
Edit: Many of my coworkers are having a similar issue so it may be something corporate-wide.
I previously had that scenario at one client, and it turned out to be a clash with a specific Add-In - ironically Microsoft's Data Mining Add-In (for SQL 2008 R2).
I suggest first turning on the Developer Main Tab in your Excel ribbon (for convenience) and then using it's Excel Add-ins and COM Add-ins buttons to disable all other Add-ins besides Power Query.
BTW performance of Power Query on Excel 2010 is truly woeful compared to Excel 2016 (where PQ is also built in, not an add-in).
BTW2 Power BI Desktop and a personal powerbi.com account are both still free.
Excel addin which uses Excel API 1.2. Add-in loads fine in Excel 2016 for Windows and Excel online. Save the file from Excel online and open in Excel 2013, addin fails to load in Excel 2013 with following errors:
When loading the Addin published in Store:
APP ERROR We can't load this app because we could not connect to catalog
When sideloading the addin from trusted catalog:
This app could not be started. Close this dialog to ignore the problem or click restart to try again
I know that Excel 2013 does not support Excel API 1.2. Could you please confirm the recommended way to make sure the add-in loads in Excel 2013?
• Should we use runtime checks using isSetSupported method?
• In such cases, how to debug which line of code is failing in Excel 2013 client?
• Is there any logging that can be enabled to troubleshoot such issues in Excel client?
I tried debugging a default add-in created by VS 2015 which uses Excel 1.2 API in Excel 2013. I added the following requirements set to the Manifest:
<Requirements>
<Sets DefaultMinVersion="1.2">
<Set Name="ExcelApi" />
</Sets>
</Requirements>
The addin also fails to load in Excel (15.0.4849.1003) when debugging using VS 2015. It works fine in Excel 2016 client.
I think there are two separate issues here (though there's a good chance that they're related, and the platform is simply giving the wrong error string. If so, let's confirm, and then I can file a bug to have us fix this).
Excel 2013 does not support the "ExcelApi" requirement set, which is a 2016 addition of the host-specific APIs (same goes for "WordApi"). If you specify ExcelApi in the requirements section of the manifest, as you have above, this will always fail to load in Excel 2013 -- by design. Essentially, you're requesting an API set and marking it as "required" for something that Excel 2013 does not support -- so it has no choice but to refuse to run it.
This is where the runtime check (isSetSupported) comes in. Please see my answer at Neat ways to get environment (i.e. Office version) for more details.
I am not sure what you mean by "how to debug which line of code is failing" or troubleshooting techinques. Essentially, any call to an Office 2016 API (anything in the ExcelApi set) from 2013 will result in a runtime failure...
Hope this helps!
I have an access 2007 application that exports data to an excel sheet and then opens the file. One user has just upgraded Excel to 2016. When it tries to export the file, I get the 'Could Not Find Installable ISAM' error. The code is simple and works on every other computer at the location, but no one else has Excel newer than 2010.
I followed the advice in the Microsoft KB article about checking for and re-registering the ISAM file - it is there and it looks fine. I repaired the office instillation and that did nothing as well.
My gut says that there needs to be a newer version of instruction to export with - I am using acSpreadsheetTypeExcel12Xml which is for Excel 2010, but Access 2007 has nothing supported newer than that. I don't have a version of Excel 2016 to test it on, but I can get on his computer from time to time. Also, I don't want to have to upgrade to Access 2010 if at all possible.
Thanks!
In MS Excel 2007 on PC you can connect to a MS Analysis Services Cube via Excel. I can't see how to do the same on Mac using Excel 2008 there.
Does anyone know how to access the OLAP cube data on Mac?
OLAP isn't supported on Mac Excel, unfortunately.
I still see negative answers for SSAS OLAP Cube with Excel 2011 Mac version. See Here
Looks not supported yet.
Cilvic : can you suggest us how you were able to connect from Mac Excel 2011?
I created a VSTO Excel 2003 addin and a setup project. It works perfect in Excel 2003 and Excel 2007.
When I install the addin in Office 2000. I getting the following error...
"The Common Language runtime could not
be loaded... contact
your administrator"
No exception Sad
Since for Office 2000 we need to use the PIA of office 2000. I created the Office 2000 PIA manually and included it in the project and build the project.
The same setup file(office 2000 pia) is working fine in office 2003/2007.
I made the copy local property to true...
Could you please help me what I am missing on this... why it is not working in office 2000...
The only suggestion I can make is to go to the msdn forums...
social.msdn.microsoft.com/Forums/