IE 11 & Office 365 - getting Excel to open instead of being prompted - excel

Windows 10, IE 11, Office 365
Desired behavior: From a website that runs reports (Crystal, but inside a custom web application), click on View Report button, Excel opens in a new window and report is displayed in Excel. Works this way on the same system but only when using Firefox.
What IE does:
Click on button to View Report, a new window opens, user is prompted "What do you want to do with xxxxx.xls" and the options Open (The file won't automatically be saved), Save, and Save As. Click on Open, Get a message at the bottom of the browser saying "Do you want to save xxxxxx.xls" with the only options being Save or Save As. Save and Open (third option) is not available. Click Save, then am prompted to Open, Open Folder or View Downloads. Clicking Open opens Excel and the report displays fine. (3 clicks to open in excel). Prior to installation of Office 365, IE 11 performed the same way as Firefox.
To my knowledge, I have the appropriate security settings selected. Any idea why this might have simply stopped working? Since Firefox works, I do not believe the issue is with configuration of Excel.
Any help, thoughts, etc. appreciated.

I hate linking a text picture, but that's what I found unfortunately.
src: https://social.technet.microsoft.com/Forums/ie/en-US/6fea6fc0-7987-47d7-a002-d73a90b1debb/asking-what-do-you-want-to-do-with-this-file?forum=ieitprocurrentver

Related

Cannot switch between popup window and Excel for Mac

I have made an Excel add-in, which pops up a window either by window.open or Dialog API.
I just tested it in Excel for Mac: when the window is opened, it seems that we can NOT put the focus back to Excel or the add-in taskpane; we have to close the window before choosing Excel or the add-in taskpane.
Does anyone know if there is a way to enable switching focus between popup window and Excel?
The dialog window is a modal in nature that forces the user to interact with it before they can go back to using the parent add-in/Office host. For interaction that requires back-n-forth with Excel, task-pane is the right place for UI.
The dialog API is meant to always show the dialog on top of other items. In terms of modality, you are correct that in Windows the dialog allows you to still interact with the spreadsheet while in other platforms, like Mac or Online is fully modal (cannot switch back to the spreadsheet). My recommendation is to design your add-in accounting for multi-platform so assume the dialog is modal in all platforms. As Sudhi recommends in his response, if your interaction requires the user to use the add-in and the spreadsheet back and forth, using a pane is a better model.

Debug Excel add-in written by JavaScript API on an existing workbook

I am trying to develop an Excel add-in by using JavaScript API for Excel.
I can already make some samples run, launch debugging under Visual Studio. Every time when i launch debugging, it opens a new workbook of Excel.
However, most of time, I need to debug an add-in on an existing workbook. For instance, here is an add-in sample, which opens a blank workbook and adds blank sheets to it. However, I want it to add blank sheets to an existing (opened) workbook. Does anyone know what I should set to debug it on an existing (opened) workbook? Should I modify some lines of code?
Edit 1:
From http://dev.office.com/docs/add-ins/get-started/create-and-debug-office-add-ins-in-visual-studio
To use an existing document to debug the add-in
In Solution Explorer, choose the add-in project folder.
Note Choose the add-in project and not the web application project.
On the Project menu, choose Add Existing Item.
In the Add Existing Item dialog box, locate and select the document
that you want to add.
Choose the Add button to add the document to your project.
In Solution Explorer, open the shortcut menu for the project, and
then choose Properties.
The property pages for the project appear.
In the Start Document list, choose the document that you added to the
project, and then choose the OK button to close the property pages.
Here is the resulting configuration that you should see:
After that just press F5 (start debugging), and you should be good to go.
~ Michael Zlatkovsky, developer on Office Extensibility team, MSFT
For anyone else running into this same issue (i.e. tying to set up an existing worksheet for debugging) without having to jump through 3 hoops to insert the add-in every time, this worked for me:
Set the Start Document to "New Excel/Word/etc Document"
Hit F5 to start debugging.
The resulting new document will be read-only and it will be in the Debug/Release folder.
Close the document, don't save it.
Copy the document to the folder where your Web Add-In manifest is and renamed it to whatever name you prefer.
Uncheck "Read Only" int the file's properties.
Set the Start Document as described by Michael in his response above.
If you start debug now, the add-in "should" load automatically. If you start without debugging (Ctrl + F5), you should be able to close the document and open it (or a copy of it) from anywhere in the PC and it should load automatically. You can even make changes to your JS code and reload the taskpanes/dialogs and it should take effect.
What did NOT work:
Using a blank start document and saving it after inserting the add-in. Once you save it, it loses its connection to the developer add-in.
If you start any document in debug mode and save it, it will NOT work the next time! If you want to make any changes to it, DO NOT start in debug mode.
I am not sure if any of these quirks are by design or if a Windows/Office update messed it up for me. Regardless, this is a very painful experience compared to developing VSTOs.

I want to display a word and excel in web browser. PDF is working but word and excel are not

Can anyone explain me how to display a word and excel in browser.
I had set content type as application/vnd.ms-excel for excel but still not working.
PDF is working fine.
You can save your word and excel files as webpage, just select that option webpage in the save as menu.
A browser is only able to display files from Microsoft Office when the application is installed. For some versions of Microsoft Office viewer applications exist.
But displaying Word and Excel files in modern browsers (especially Internet Explorer) has the drawback that the browser does not display the file in the original window but rather opens a new window.
This in turn is good because current MS Office versions hide some functions and windows when a file is not opened in the application but in the browser. This sometimes makes it impossible to uses formulas in Excel or reopen a file that was opened in readonly mode.
In short: if you want a good experience for your users either accept (if they have it installed) that a second window is opened for the Word and Excel file you present or (if possible) convert it into a html equivalent (which will have a different look) or a pdf (which then automatically is readonly and kind of protected)

Can not open an Excel document from SharePoint

My problem occurs only for Excel files from a SharePoint 2003 WSS2.
I meet the problem with all versions of Internet Explorer
Details of the problem:
When clicking on the Excel file (screen 1) a pop-up appears offering the choice to open or save the file (screen 2).
Saving the file works fine but if I select "Open" the pop-up close, then the page becomes blank. And my document does not open :(.
This problem does not occur when opening files with a different file extension.
With the same browser, if I open an excel file not stored in Sharepoint (i-e in another website), I can open the file successfully. Despite my attempt multiple searches on the net I hope to find my solution with you.
The problem may have started with the installation of Office 2013 on the computer, but I'm not sure.
Screen 1
Screen 2
The translation of the buttons are "Enregistrer" = "Save" "Enregistrer sous " = "Save as" "Ouvrir" = "Open"

How do I make an Office 2013/2016 application run in separate process on Microsoft Windows?

I am developing a Excel plugin. It works all right for Excel versions before 2013. But a lot of features is broken when it runs against Excel 2013. I found the root cause is all windows are running in only one process in Excel 2013. Even if user explicitly launch a new window by double-clicking the shortcut on the desktop or by clicking the item in the start menu, no new process is created.
This results in the status conflict between processes. Status bar and ribbon is shared. For instance, when I update the status bar information in one window, the other windows' are also updated. When I check/uncheck a ribbon button in one window, the other windows' buttons are also checked/unchecked.
I think a possible solution is to change some configurations to make it work as before. But I found nothing relevant by searching on google.
Does anyone know how to make it or is there any other solution?
With Excel 2013, the default you have is to create a new window within the existing Excel process. In order to force the creation of a separate instance of the Excel process, you have these options:
Option 1
From the command prompt, run EXCEL /X and you will open Excel window as a new instance. The /X command switch forces the creation of a new instance.
Option 2
Right click on the Excel icon in Windows taskbar
Go down to where it lists the application
Hold down the ALT key on the keyboard and click "Excel 2013/2016"
It should give you this prompt, "Do you want to start a new instance of Excel?"
Click "Yes!"
Option 3
Use this technique to open an existing document directly:
Hold down Alt.
Right click Excel file.
Click Open.
Continue holding down Alt until the "Do you want to start a new instance of Excel" dialogue pops up.
Click Yes.
For more detail,please visit:
http://sqlblog.com/blogs/marco_russo/archive/2012/07/24/running-excel-2013-in-a-separate-instance-excel-powerpivot.aspx
re. "Right click on the Excel Tab in Windows taskbar keeping the ALT key pressed"
-This option is not available in Windows 10 with Excel 2016.
However, the Excel /X option works and a second change-undo buffer is created, as noted above, in the new process.

Resources