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?
Related
I am trying to convert an old Excel add-in to a new VSTO version. The present add-in reads data from an open Internet Explorer browser.
Since I.E will no longer be supported shortly, I am looking for a solution with an advance developing technology. The above issue is a major point without which this solution ill not be applicable.
Any help with a sample snippet will help.
There are instructions online for sideloading an addin into Excel for Windows.
However, I get stuck on step 4. Namely, there is no Manage My Add-in's button anywhere within the MY ADD-INS page that I can find.
Does this button still exist somewhere, or are the instructions out of date? If the button is gone, is there any other easy way of side-loading an add-in into Excel?
There are other instructions online for sideloading an add-in, but they are much more complicated and hard to follow.
Thanks for any information!
The page that you linked to is for sideloading in Excel on the web, not Windows. For Excel on Windows, see Sideload Office Add-ins for testing. BTW, its best to work with the help on the learn.microsoft.com domain. The GitHub repo that you linked to is the source files and its harder to find your way around there.
I have a client who is asking me to fix an issue they are having with Microsoft Project.
The issue is that they are attempting to open a task list on SharePoint Online via the 'Open with Project' button in the ribbon, but after the alert asking them if they would like to open it in Project 2016 pops up nothing happens.
I have set up a fresh SharePoint environment and tried it at my end, but I get the same problem. There is no error message (as an alert or in the console) and I have wracked my brain and come up dry.
What I have tried:
New SharePoint instance.
Fresh Microsoft Project install.
Looked at the site/site collection features
Multiple browsers (specifically Chrome, IE and Firefox)
The issue is the same no matter what I do.
Has anyone else come across this problem before and, if so, how did you solve it?
Are you using 2016 Click-to-run (C2R) or MSI version? Can you share the build number from winproj.exe?
If you are on C2R version, can you try making the following registry edits (save the following as a .reg file and run it) and see if it helps?
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides]
"ofhdegpklv1irq0"=dword:00000000
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides]
"ofhdegpklv1irq0"=dword:00000000
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).
I've been working intermittently on an Excel spreadsheet for a customer that does some pretty intense calculations. We implemented a security procedure using VBA... At first the requirements were relatively simple, and the overall lack of security in a spreadsheet was discussed and well understood.
Since then the customer has decided that he would like to have the sheet a bit more secure. Under normal circumstances I would simply disable the developer menu via code. Unfortunately I just recently found out that the customer, and many of his customers, are using Mac Office. (There are some customers that are even using 2008 and they found out the hard way that 2008 stopped supporting VBA)
My question is; is it possible to disable access to the Visual Basic editor in Mac Office in versions Pre 2008, and versions 2011 and after since from the research I've done so far points to a return of VBA support in Mac Office in 2011.
Unfortunately I do not have access to a Mac Office version to even really look through the application and or/test different solutions. In Windows it is possible to right click the VBA project and choose protection from the VBAProject Properties and choose "Lock project for viewing". Does this option exist and is it effective in Mac Office?
Any help/suggestions would be greatly appreciated.
I'm pretty sure you can lock projects in Mac Office the same way you can in Windows. Keep in mind that a project that has been locked in one version of Excel cannot be unlocked with a different version. So, if your customer needs to be able to unlock, they will need to use the same version of Excel you used to lock it.