4 ms·
It is great that Microsoft is investing in Office again. I just got upgraded at work from office 2007 to 2016 (we like to take our time, I was on WinXP not so l
by cm2187 8y ago
It is great that Microsoft is investing in Office again. I just got upgraded at work from office 2007 to 2016 (we like to take our time, I was on WinXP not so long ago), and I can barely see the difference. They changed some colors, there are menus that open in a panel instead of a modal box. I don’t think a single user cares about these changes (and they seem to have carefully preserved the bugs). And the problematic UI (for instance the tiny non resizable modal when you click the fx button) have not been updated.
But there are still massive pain points or improvements that could be added. For instance:
- linking between excel and powerpoint. Almost anyone who will show an analysis, whether in a bank, accounting firm, consultant, etc will prepare some table and charts in excel and will want to use them in powerpoint. The link between the two is unstable, screws the formatting, or requires lots of manual steps.
- Microsoft should really look into Apple’s take on excel, with a sheet being a canvas on which you can add tables, charts, the tables have scroll bars if they overflow. Instead of the rigid single grid per tab, where if you show two tables one over the other you need to align the columns even when they have different data types.
- VBA hasn’t been updated in 20 years and it clearly shows. There needs to be a more modern scripting language. I have heard rumors about javascript. Not convinced it’s a great choice, but that would still be better than VBA.
- pjmlp 8y agoI can tell you one big difference, the set of statistic formulae that are now available.
- fxfan 8y agoYou clearly missed out on the magical fill. Search for Sumit gulwani excel. Another collaboration with MSR
- hliyan 8y agoThis is a headache for me too: with a sheet being a canvas on which you can add tables, charts, the tables have scroll bars if they overflow. Instead of the rigid single grid per tab, where if you show two tables one over the other you need to align the columns even when they have different data types Another thing I'd like to see is to be able to treat cells as objects rather than single scalar variables. For example, to represent data that has more than two dimensions.
- kgwgk 8y agoMicrosoft want’s to kill VBA but customers won’t allow that. https://en.m.wikipedia.org/wiki/Visual_Studio_Tools_for_Office https://en.m.wikipedia.org/wiki/Visual_Studio_Tools_for_Offi... may make sense for developers, but users like the ability to do things in the “wrong way”.
- cm2187 8y agoVSTO isn't great. There was something called VSTA earlier, basically a little visual studio embedded in Office, you could do with any .net language what you could do with VBA. Unfortunately they canned it.
- kgwgk 8y agoDid VSTA for Excel ever exist? I can find only references to InfoPath (whatever it is, it seems it was part of Office for a while).
- cm2187 8y agoNo it never existed. But I believe that at one point it was the intention, it was meant to cohabit with VBA, and work essentially in the same way.
- clausok 8y agoEspecially with ExcelDna, it's hard to make an argument for using VSTO. And even with ExcelDna (i.e., an xll written in F#\C#), I find there are still niche areas where vba is effective, particularly when working with the Excel object model. The split I like is to have vba orchestrate interactions with the object model, Sheets, Books, Ranges, Range.Find(), etc. So for example, have your F#\xll code parse "60d" into the last 60 trading days, and then use vba to select those days in Excel's autofilter.
- cm2187 8y agoPossibly stating the obvious, but you know that you can manipulate the excel object model from ExcelDNA in the same way that you can with VBA (thanks to VSTO!). Add a reference to Microsoft.Office.Interop.Excel, and get a handle on the Excel Application object using ExcelDna.Integration.ExcelDnaUtil.Application. Alternatively you can use the excellent NetOffice.Excel (instead of Office.Interop.Excel), which will have less functionalities but with better version support.