I have MS Office 365 on my work computer and keep on getting this error.
I have tried the solutions here:
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_other-mso_2010/run-time-error-453-cant-find-dll-entry-point-solv/c188ea01-7eda-4b46-b43b-64695fc3ce8f
but they don't really work since I'm on Office 365, so there's not a separate MS Excel install, it's just a MS Office install. I've tried repairing, both quick and full, and restarting my computer.
All I am trying to do is to open solver. Any solutions?
Thanks!
I had the same issue with Office 365. My IT department installed an update and it fixed the problem. Apparently, I was only getting updates every 6 months versus monthly updates.
Related
The web store 'Open In Excel' button does not work for Mac users. Excel indicates that it is downloading some file but then nothing happens. I'm sure expected behavior is that the workbook should open and install the add-in to Excel. Here is a video showing this, on Excel v16.40 (latest version as of this writing):
https://drive.google.com/file/d/1MqlZyqhYe9MfOzJN_sjpFwyPHOn4LuPD/view?usp=sharing
I became aware of this issue because some of our customers have contacted us, asking why the add-in wasn't working. Who knows how many potential customers we have lost because they simply thought the add-in wasn't supported on their system and moved on.
Is this a problem with our add-in code? Is anyone at Microsoft aware of this issue?
I Have an add-in that is working on Excel in chrome, excel in Edge, but doesn't work in excel desktop.
Any clues?
Thanks
In the article amitklein gave, it says:
Office will still use the EdgeHTML base for add-ins until a build of Office 365 that supports Chromium is installed on the computer. We expect these builds to ship in 2020. They will likely appear in the Insiders channel in the first half of the year.
I haven't found the Chromium based Office 365 in insider channel so I think the version for now is still EdgeHTML based and Excel uses Edge Legacy.
All VBA projects fail to work, if you use Excel, the VBA project deleted when trying to open the workbook, if it is Access, no application works because it does not find any project.
For what I've had been researched and tested, apparently the reason is the Windows 10 update, I focused exclusively on the Office 2010, seeing macros, security, library references etc, but it seems that Windows is the problem and not the Office itself. This problem appeared 3 days ago, before that everything worked fine.
I would appreciate your help if someone else had the same problem and how you solve it.
I have Windows 10 Home, and I tried with Office 2010 (my original base Office) and then I install Office 2016 hoping to solve it, but nothing works.
Thank you very much in advance.
uninstall and install again Office 2010 with all the features (including VBA).
Macro security fully enabled
VBAProject references ok
Microsoft Visual Basic for Applications install correctly.
Install Office 2016, to try if the problem solved
Reinstall Windows 10 Home 64 to the factory line.
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!
I am supporting a legacy application that was written in Access 2003 using VBA. We are updating our systems to Office 2010, with the exception of Access, which will remain the 2003 version. (This is due to several factors pertaining to other groups in my organization.)
We use Access as a front end for running reports out of MS SQL and Sybase databases. Some of these reports open in Excel. During testing, running reports that write to an Excel workbook causes the Access application to crash and exit without a warning message - the application simply disappears from the screen.
I'm not sure what the cause of this is or where I should start looking for answers. Has anybody dealt with a similar situation?
I saved and recompiled the application on the development machine that had Office 2010 installed, and thereafter the application worked correctly with Office 2010 (of course, it no longer works on machines only having Office 2003.) This was, of course, after checking the references were correct. Without any intervention, the reference to Office was for 2010.
After testing with early versus late binding, it would appear the best answer to this issue is to use late binding.
Make sure you are writing to Excel in Excel compatibility mode (.xls).