Editing Office 365 Excel Doc in Excel Office 2013

I have an excel document with macros uploading on Office 365. I understand that I can't use the macros in excel online so I want to edit in excel. When I click 'Edit in Excel' the program opens but the actual document doesn't. I am able to download a copy
though. How do I get the document to open?
Thanks

Hi,
Does this only occur to this specific Excel file? or all Excel files?
Let's first test with a simple Excel file without macros, or disable the macros in that specific file, upload it to Cloud, then try again. This will help to narrow down whether the issue is with the macros.
Please feel free to post back with any findings.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Similar Messages

Office 365 Home Premium (2013) vs Excel Standalone (2013) - Looking for Power Pivot

Hi I have read a few comments here on this site but still have a question about the topic.
I currently have an OEM Office 365 Home Premium with Excel 2013 in it but no power pivot available. My objective is to get Power Pivot. Can anyone advise how can I do that? I installed my Office 365 using Click-To-Run so I don't think this allows me to disable
any specific application e.g. Excel 2013 that's bundled with the rest of Office 365 I purchased.
I heard that Excel 2013 Standalone can be bought and downloaded and it does come with power pivot add in. Is this true? If so can I buy the Excel 2013 standalone then run it side by side with the Office 365 Home Premium I have now installed or
will it clash and have issues when used together ?
MS official sites say you can only get the power pivot as add in if you purchase Office 365 Plus. I'm a bit confused. If that is true does it mean the Excel Standalone has no power pivot available?
Thanks and I'm looking for any seasoned user who can share their experience using Excel 2013 standalones or users with 365 having version 15.0.4649.1001
Thanks - Felix

Hi,
Power Pivot are available in the Office Professional Plus and Office 365 Professional Plus editions, and
in the standalone edition of Excel.
http://office.microsoft.com/en-us/excel-help/start-power-pivot-in-microsoft-excel-2013-add-in-HA102837097.aspx
Then, please note the following thing when you install Office 365 and other Office version side by side.
As you said, Office 365 usually uses Click to Run version(C2R), and Office 2013 MSI on a system with Office 365 (Click to Run) is NOT supported, thus, we need to install the C2R version of Excel 2013 standalone edition.
Quote From:
http://social.technet.microsoft.com/Forums/en-US/7cd0edc4-36fc-4553-9b6c-f27078005686/deploying-office-365-pro-plus-on-systems-with-existing-office-2010-2013-installations?forum=officeitpro
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

2013 Excel docs open up to grey screen (Office 2013 Home and Business)

What I have tried:
-Opening in safe mode (using shift).......still shows grey blank screen.
-File>Options>Advanced> "Ignore all other applications using DDE" check marked......Still shows blank screen.
-Don't have the option to click "unhide" because every tool option is greyed out.
***When the 2013 excel doc opens up to the blank grey screen, ALL the menu tools and options are grayed out as well. I cannot click on anything besides File>New or Open or Account or Options.***
Please help me with my direct problem. I have been everywhere on the internet and no one has my particular problem that i have found. There are similar ones but those solutions i have already tried. (See Above)
Thanks

Hi,
First, try to repair Office 2013 to check the issue.
Second, try to reapply the registry patch:
reg add HKCU\Software\Microsoft\Office\12.0\Excel\Options /v NoReReg /t REG_DWORD /d 1
Jaynet Zhang
TechNet Community Support

Office 2013 Home & Business Edition - None of the application (Word, Powerpoint, Excel or Outlook) is opening, not even in safe mode..

Office 2013 Home & Business Edition - None of the application (Word, Powerpoint, Excel or Outlook) is opening, not even in safe mode.. I tried to run the application in compatibility mode by right clicking the excel.exe and choosing the compatibility
mode, still no success. It is installed on Windows 7 Professional SP1. All the latest updates are already installed. I have also tried Microsoft fixit, but still no Success. Please help!!

I'm so sorry that I forgot the Office programs even not open in safe mode and provide useless information in my last reply.
The problem persists when we perform a Windows clean boot, right?
Were the Office programs suddenly not working? Or it just can’t be open after you install it? Did you get any error message?
If you haven’t try a repair of your Office installation, we can try it to check the result:
http://office.microsoft.com/en-us/project-help/repair-office-programs-HA010357402.aspx
In addition, try to use Event Viewer to see if we can get some useful error log about this problem. See:
http://windows.microsoft.com/en-us/windows/open-event-viewer#1TC=windows-7
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Microsoft Office 2013 (Word,excel) Still appear as "Standard" after migrate in ProPlus 365

Hi,
I'm planning a mass deployment of Microsoft Office 365 ProPlus with SCCM 2012.
I made my application, and added a supersedence of Microsoft Office 2013.
So when I deploy ProPlus, It first uninstall Office 2013, then reboot, then install Office ProPlus 365
My problem is that when it install Office ProPlus product that I had on Office 2013 and I go in Account tab, I still see "Microsoft Office Standard 2013"
When I see the others product, I see Microsoft Office ProPlus.
I'm sure that Standard is uninstalled first, I can also see in Add/Remove programs that there is no Standard version.
Is that just a bug, or some of my product hasn't migrate on Office 365 Proplus ?
Thanks ! :)

@Don, I reboot the client computer after uninstalling Office 2013. Nothing have changed.
@Aravindhan, I'm lauching Office from the start menu. I already tried to just uninstall Office and see what's happen. Office uninstalling correctly. But When I install ProPlus, I can see "Office Standard" in account tab.. (and Standard doesn't
appear in Add/remove programs)
Maybe check c:\windows\temp\SetupExe(YYYYMMDDHHMMxxxxx).log
This is the Office (MSI) setup logfile, to see if there were any uninstallation errors?
Are there any standalone Office products installed previously, e.g. SharePointDesigner or similar ?
It might be necessary to use OFFSCRUB.VBS (from the Office removal Fixit) to clean that up?
http://blogs.technet.com/b/odsupport/archive/2011/04/08/how-to-obtain-and-use-offscrub-to-automate-the-uninstallation-of-office-products.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Cannot open Office 2013 Excel, Word, PPT Files on Network Share

Cannot open Office 2013 Excel, Word, PPT Files on Network Share
I am having a problem opening any Office 2013 file when it is located on a network drive. I immediately get the error:
"Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space.
. To make more memory available, close workbooks or programs you no longer need.
. To free disk space, delete files you no longer need from the disk you are saving to."
It only occurs when I try to access the file when it is stored on a network share. I cannot open any word, excel or PPT files located on my file shares.
I am on Windows 8 (pro), part of a local domain based on Server 2003, and have administrator rights to the domain and the file share where the Excel file resides (and Word files -same problem). If I copy the file locally, I can either open
it directly, or right-click, go to Properties and 'un-block' the file and then open it. But it is impractical to keep doing this, as I edit different files from the directory tree all day.
I have bing'd and google'd this extensively, and the only answers I come up with do not work, such as going into the DCOM config system and changing the user from interactive to launching user, or vice versa, or even using a specific user - mine
with the password. Since the product is so young there aren't a lot of posts on this, and nothing has improved the situation.
Can you add any insight to this? I really want to use Office 2013, but this is such an obstacle I'm going to have to downgrade if this problem cannot be resolved. Thank you very much for any help you can offer.
Evan

Dear Evan,
If DCOM config solution did not work, I'd suggest narrow down the problem by trying to access another network share on another server, try to open an Office file there, do we still have the error? It could help us determine if the issue is on the client
machine or the server side.
Best regards,
Daisy Cao
Forum Support
Please take a moment to "Mark As Answer" if they help.

Can't open .dz attachments in Outlook to Excel in Office 2013

We have a custom ERP we use at our company that creates .dz attachments which our users can open in Excel. In order for the employees to open these .DZ files in Excel we needed to make a registry edit.
I just upgraded machines to Office 2013 and now we have the same problem. We don't remember what the registry fix is and hope someone can point us in the right direction.
Thanks in advance.
IT

Yes, it can't be opened as an attachment.

? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
Most of our users are still using older desktop windows PCs and Office 2003! We are beginning to upgrade to laptops running Windows 8.1 with Office 2013. Of course, we IT technical people are using the new laptops first. These new laptops are
64 bit.
Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
commands, but "...Starting from Office 2007 the Fluent UI is used instead." In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
create a basic incompatibility to opening these spreadsheets in Office 2013.
For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library."
For example, the following code snippet:
Private Sub Workbook_Open()
For Each bar In Application.CommandBars
bar.Enabled = False
Next
results in: "Compile error: can't find project or library."
(Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
Are you aware of a quick VBA workaround to get by this?
•I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
Alternatives would be:
•Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
•Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
Thanks
Basic compatibility issue that seems solvable:
Opening these spreadsheets displays this error:
Compile error:
The code in this project must be updated for use on 64-bit systems.
Please review and update Declare statements and then mark them with the PtrSafe attribute.
This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

Hi Allan_L,
Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Move a Excel 2010 Dokument Addin Project (Visual Studio 2012) to another devleopment machine with Visual Studio 2012 , but Office 2013

Hi
we do have the following situation
on computer A there is a Excel Document Addin development project , Visual Studio 2012, Office 2010 installed. All works fine.
we would like to bring the project to another machine with Visual Studio 2012, but Office 2013 installed.
Visual Studio can not build the project. It says that the application is not installed on the machine (though Excel 2013 is installed , but not Excel 2010) It seems to have a problem with the
vbproj.
In other forums I found a hint that "Hostpackage = ..} needs to be set accordingly in the vbproj. I created then a "empty Excel-Addin project" under Visual Studio , looked at
the Hostpackage entry, put that into the vbproj of "problem project. It still does not work.
It would be great if anyone could help.
Thomas

Hello Eugene
Problem is that it says that projectboard (the name of the main project) can not be loaded. All other projects in the solution can be loaded. Strange thing is , now that I try to create a empty excel Project it says that according to Excel security settings
it can not be generated !?
I opened then Excel and set all Trust Center settings to "Default" - but no effect. I really have no idea what is wrong ..!?
Tom

Will macros in excel work properly if I switch Office 2013 32 bit to Office 2013 64 bit?

hi,
Will macros in excel created with Office 2013 32 bit work properly if i switch to Office Execl 2013 64 bit?
Thanks

Hi,
As far as I know, most of the macros might work well between 32bit and 64bit Excel. But there are some limitations for Excel 64bit:
Solutions using ActiveX controls library, ComCtl controls won’t work.
Third-party ActiveX controls and add-ins won’t work.
Visual Basic for Applications (VBA) that contain Declare statements won’t work in the 64-bit version of Office without being updated.
Compiled Access databases, like .MDE and .ACCDE files, won’t work unless they’re specifically written for the 64-bit version of Office.
More reference:
https://msdn.microsoft.com/en-us/library/ff700513(v=office.11).aspx
https://msdn.microsoft.com/en-us/library/ee691831(v=office.11).aspx
https://support.office.com/en-sg/article/Choose-the-32-bit-or-64-bit-version-of-Office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261?ui=en-US&rs=en-SG&ad=SG
If you have any further question about macros, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Excel Calulates twice when set to Automatic in Office 2013

I have had a group of users who have raised an issue with Office 2013 running far slower for a number of spreadsheets. After investigating the fault, I have identified the issue as being due to the way in which Excel appears to be handling the calculations.
When I open the spreadsheet myself, on Office 2013 32 or 64 bit, I am asked to update the data, at which point the spreadsheet runs the calculations if I accept, and then runs them again. If I set this behaviour to manual, I can open the spreadsheet, request
an update, and then manually calculate, which only takes one pass at the data but provides the same results. The behaviour does not persist on an Excel 2010 machine, which does only a single pass on both manual and automatic. The spreadsheet does pull data
from an external sheet, but as this only occurs in Office 2013, I don't believe this to be intended behaviour.
Is there anyone who can shed some insight into why this acts this way, and how to prevent this. We are trying to upgrade our business to 2013, and are getting a huge amount of push back from this particular set of users over this issue

Hi,
According to your description, my understanding is that you want to calculate once time when the file opening or update data.
I suggest you can make the file always calculate manual.
You may try to do following steps:
Click File>Options>Formulas> Calculate Options> Manual
Then you can save it .
For more detail information, please refer to the following link:
http://office.microsoft.com/en-us/excel-help/change-formula-recalculation-iteration-or-precision-HP010054149.aspx
The article applies to Excel 2007, but we can refer to it.
Regards,
George.zhao

Windows 8.1 - Office 2013 - Visual FoxPro - excel data connection problems

Hi i have an excel document with existing data links to a foxpro database. these links worked on windows 8 with office 2013 but since getting windows 8.1 the links no longer work.
After much searching i have found i need to installed VFPOLEDBSetup.msi
This does not fix the issue. The ODBC Data sources located Control Panel\All Control Panel Items\Administrative Tools still have no reference to FoxPro and within excel if i select from other sources and the other/advanced i can see the Microsoft OLE DB
provider for visual fox pro but it crashes excel.
in Windows 8 ODBC Data sources located Control Panel\All Control Panel Items\Administrative Tools i have listed two items Visual FoxPro Database and Visual FoxPro Tables but both these are missing in Windows 8.1.
What do i need to do to correct other than not to use Windows 8.1
Many Thanks

Hello,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
Thanks,
George Zhao
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click "[email protected]"

Office 2013 - Excel 2013 - "This action is only valid for products that are currently installed."

I had Office 2010 starter and Outlook 2010 installed. I recently purchased the Office 2013 click to run version (paid monthly subscription) and installed Office 2013. After installing 2013 I noticed that when I opened up Excel files they would
still open in Office 2010. I uninstalled Office Starter 2010 and uninstalled Outlook 2010.
I then manually fixed the file associations for Word, PowerPoint, Publisher and such, however I could not manually fix the Excel file association.
Excel documents show the correct icon however when I double click on them the following error appears "This action is only valid for products that are currently installed."
I have used the Office 2013 repair process, I have uninstalled and reinstalled Office 2013, I have manually uninstalled office 2013 using KB 2739501 (
http://support.microsoft.com/kb/2739501/en-us ) and I still can not open Excel documents.
Recently I found that I can not do mail merges either using Excel documents as the data source and I believe the two items are related.
Any suggestions?

Hi,
Please try to turn off compatibility mode and then check the issue again. To do this, please follow:
1. Open this folder location:
For Windows 32-bit: C:\Program Files\Microsoft Office\Office15
For Windows 64-bit: C:\Program Files (x86)\Microsoft Office\Office15
2. Find Excel.exe, right-click it, and choose Properties.
3. Click on the Compatibility tab and ensure that all of the boxes are
un-checked.
For more information, please refer to this:
http://support.microsoft.com/kb/2674519/en-us
Thanks,
Steve Fan
TechNet Community Support

Excel connection manager - Error after Installing Office 2013

Hi Team,
My SSIS package used to work fine until I Upgraded my Office 2010 to Office 2013. After upgrading to 2013, the SSIS package which is created using SQL 2012 is throwing error for Excel Connection manager. Below is the error what I see
TITLE: Microsoft Visual Studio
Could not retrieve the table information for the connection manager 'Excel Connection Manager'.
Failed to connect to the source using the connection manager 'Excel Connection Manager'
BUTTONS:
OK
FYI, I am running the package with Run64BitRunTime property = False.
Do let me know the solution please. It will be of great help as we are proposing this tool in a migration project.

I found the solution. Thanks
You don't need office on your server (not recommended and not supported). You should install
Microsoft Access Database Engine 2010 Redistributable for excel (xlsx) files and then use the Excel
This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and *.accdb) files and Microsoft Office Excel 2010 (*.xls, *.xlsx, and *.xlsb) files to
other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats.

Windows 8.1 Hangs, Crashes, Office 2013 Excel Crash

I'm an IT professional (over 20 years). I feel qualified to make these statements in this post. I also know that the download sites for Windows 8.1 never give any warning as to what works, what doesn't, driver updates needed etc. In fact it's
being sold as the next best thing! Just download and upgrade. There's even a tool I ran that told me my laptop was ready to go!
My environment is an HP 6530B laptop that worked flawlessly on Windows 7 professional with IE10. I upgraded to Windows 8.1 about 6 weeks ago (upgrade went flawlessly) and have had nothing but nightmares. Here's the list, so beware.
Blue Screens are frequently seen. I was able to reduce them by clearing out all the UPDATEs and applying a select few of them. How can updates make things worse?
System Hangs, forcing a power down 3 to 4 times a day.
IE11 crashes, sends a dump to MSFT and reboots itself at will about 5 to 7 times a day.
Certain Monitors used as a second monitor that worked in Windows 7, cause the system to go haywire and become unusable no matter how many times you reboot.
Automatic updates and manual update checks frequently don't work well. If you press the Check Upates button multiple times, you will get different results.
Some updates make matters worse
There appears to be random memory leaks in the Service Host process
Service Host process group frequently hogs memory 1.5 GIG or more. (These are all MSFT services) It is believed that some of these processes have a memory leak.
Office 2013 is unstable when using either Word or Outlook (will hang system)
Excel 2013 throws errors when connecting to the TFS Team client to download Workitems, it can seem to interpret the data.
Excel 2013 (issues, problems, crash) will crash on simple moves of area data from one group of cells to another.
VS2012 will hang and WINDBG cannot be attached to debug the process
VS2013 works much better!
Starting up Cisco's VPN client 5.0.07.0290 will hang the system 1/2 the time.
Some installed products such as Infor's EPAK crash and burn when used.
The only good thing about Windows 8.1 is Google Chrome because it ran fine!
To me this is the worst production roll out I've ever seen from the team that produced the platform we've adopted. I can't flog anyone, but I can post an honest assessment of my experience.
JP Cowboy Coders Unite!

Turns out I have a computer that doesn't have a specific driver for MSFT's brillant move to change things up in Windows 8.1. This content came straight from Intel site.
Which Intel graphics products have drivers for the Windows 8* and Windows 8.1* operating systems?
Intel® Graphics:
Windows 8 driver available?
Windows 8.1 driver available?
4th Generation Intel® Core™ Processors with Intel® Iris™ Pro Graphics 5200
Yes
Yes
4th Generation Intel® Core™ Processors with Intel® Iris™ Graphics 5100
Yes
Yes
4th Generation Intel® Core™ Processors with Intel® HD Graphics 5000
Yes
Yes
4th Generation Intel® Core™ Processors with Intel® HD Graphics 4600
Yes
Yes
4th Generation Intel® Core™ Processors with Intel® HD Graphics 4400
Yes
Yes
4th Generation Intel® Core™ Processors with Intel® HD Graphics 4200
Yes
Yes
3rd Generation Intel® Core™ Processors with Intel® HD Graphics 4000
Yes
Yes
3rd Generation Intel® Core™ Processors with Intel® HD Graphics 2500
Yes
Yes
2nd Generation Intel® Core™ Processors with Intel® HD Graphics 3000/2000
Yes
No
Intel® Atom™ Processor Z2760 with Intel® Graphics Media Accelerator
Yes (from computer manufacturer only)
Yes (from computer manufacturer only)
Intel® Core™ Processors with Intel® HD Graphics
Yes1 (from Microsoft Windows Update only)
No
Intel® Celeron® Processors 700/800/B700/B800/G400/G500 Series (formerly codenamed Sandy Bridge) with Intel® HD Graphics
Yes
No
Intel® Celeron® Processors 900/1000/G1000 Series (formerly codenamed Ivy Bridge) with Intel® HD Graphics
Yes
Yes
Intel® Celeron® Processors 2000 Series (formerly codenamed Haswell) with Intel® HD Graphics
Yes
Yes
Intel® Celeron® Processors J1000/N2000 Series (formerly codenamed Bay Trail M/D) with Intel® HD Graphics
Yes
Yes (64-bit only)
Intel® Celeron® Processors P4000/U3000 Series (formerly codenamed Arrandale) with Intel® HD Graphics
Yes1 (from Microsoft Windows Update only)
No
Intel® G41/G43/G45/Q43/Q45 Express Chipsets
Yes1 (from Microsoft Windows Update only)
No
Intel® Pentium® Processors 900/B900/G600/G800 Series (formerly codenamed Sandy Bridge) with Intel® HD Graphics
Yes
No
Intel® Pentium® Processors 2000/G2000/G2100 Series (formerly codenamed Ivy Bridge) with Intel® HD Graphics
Yes
Yes
Intel® Pentium® Processors 3000/G3000 Series (formerly codenamed Haswell) with Intel® HD Graphics
Yes
Yes
Intel® Pentium® Processors G6000/P6000/U5000 Series (formerly codenamed Arrandale/Clarkdale) with Intel® HD Graphics
Yes1 (from Microsoft Windows Update only)
No
Intel® Pentium® Processors J2000/N3000 Series (formerly codenamed Bay Trail M/D) with Intel® HD Graphics
Yes
Yes (64-bit only)
Mobile Intel® 4 Series Express Chipset Family
Yes1 (from Microsoft Windows Update only)
No
JP Cowboy Coders Unite!

Excel COM object calls break with Office 2013 upgrade on 64-bit OS?

Out of the 1000+ computers in the company mine is the only one running 64-bit windows 7. I have noticed that when i try to run a small DLL i created to convert Excel files to Tab Delimited files it is crashing only on my computer.
I have debugged the source code and found that there is no real exception being thrown except a popup does appear in the background stating "We're sorry, but Excel has run into an error that is preventing it from working correctly. Excel will need to
be closed as a result. Would you like us to repair now? [Repair Now][Help][Close]"
If i open excel via the main application this same popup comes up and when i click repair excel closes. when re-opened Excel re-activates and then works fine.
here is a sample of my (VERY simple) code which has worked for years on office 2007 with 64-bit OS:
Dim excelPath As String = "C:\test.xlsx"
Try
objXL = CreateObject("Excel.Application")
With objXL.Application
.displayalerts = False
.Visible = False
.workbooks.Open(excelPath)
.Workbooks(ExcelFileName).SaveAs(csvPath & csvFileName, Excel.XlFileFormat.xlCurrentPlatformText, , , , , Excel.XlSaveAsAccessMode.xlNoChange, , , , , )
.workbooks(csvFileName).Close(csvPath & csvFileName, savechanges:=True)
End With
Catch ex2 As Exception
Throw ex2
Finally
objXL.Quit()
objXL = Nothing
End Try
I have isolated the exact line that is causing the exception to be thrown...
.Visible = False
Why would hiding the Excel UI cause an error of "We're sorry, but Excel has run into an error that is preventing it from working correctly" to be displayed?
If i remark out this line then the application seems to work properly for me...

That I do not know. Do you have another machine where Office 2013 is installed, and where you can test? It could be system configuration issue, could be a change in the application behavior or a difference between 32-bit and 64-bit. You are updating
at least a couple of generations of software and now running in a 64-bit environment so there is always the potential for changes in behavior and software defects.
Unfortunately, I do not have Office 2013 64-bit installed so I cannot test this scenario.
You could also try posting to the
Excel for Developers forum to see if anyone has encountered the same issue when using Excel automation.
Paul ~~~~ Microsoft MVP (Visual Basic)

Editing Office 365 Excel Doc in Excel Office 2013

Similar Messages

Maybe you are looking for