You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
Before I carry on digging into the details of the new and improved features in Excel 12, I wanted to make sure everyone had a good sense for the work we’ve done in this version. When we were planning Excel 12, we spent a significant amount of time talking to a wide variety of customers. One theme that emerged clearly was that customers wanted to see continued innovation and improvement in the core aspects of spreadsheeting – working with data, formatting & printing, writing formulas, charting, etc. Another theme that we heard was that customers wanted to use spreadsheets in ways that they currently couldn’t (with more data, on the server, etc.). We used this feedback as the impetus to take a hard look at all of the essential parts of spreadsheets – from the core architecture to the experience of working with data to the experience of sharing information – and to identify new directions we could take over time.
What follows is the resultant list of areas where we have done work in Excel 12 (many in conjunction with other Office teams). In Excel 12, we have:
This isn’t a complete list, and I will get into more detail (with screenshots) in each area as I write more, but hopefully this gives you a better idea of the amount of work that’s going into this release. We’re really proud of the work, and we look forward to sharing the details with you. Next week, I will spend some time discussing the investments we have made in the area of conditional formatting.
Comments: (18) Collapse
"Made connecting to external data more straightforward and added connection management capabilities to the product"
Does this also include ADO.NET?
"Created a new class of functions that return data directly from SQL Server Analysis Services"
Will it also be backward compatible or only targeting SQL Server 2005?
Kind regards,
Dennis
David,
Great advancements so far. I'm excited to see it.
A few questions:
Does this mean that the calculation engine will support multiple CPUs?
With the new Conditional Formatting enhancements, will it be possible to configure a Conditional Number Format?
eg. eg when true #,##0.0, when false 0.0000 ?
Could you please reveal some of the new function names available?
Will there be any reverse lookup functions along the lines of the post:
groups.google.com/.../31684311d468a900
The bigger picture again - the future of Excel versus databases. The new Excel will be able to handle much larger amounts of data than currently.
I can imagine some simple improvements to pivot tables - formatting. But, for me, the current functionality of Excel needs little improvement. I can envisage more database-type functionality within Excel - such as a report similar to from a database. And evolutionary upgrades to the sort of capability exposed in MS Query.
My thoughts are that the software will be enormously powerful and most of that capability will be underutilised. This leads me to think that more focus would be valuable on improving the 'smartness' of the application to help users. And, I guess that is what is happening?
It seems to be less the software's functionality that needs improvement but the skills/'smartness' of users.
best regards,
Pete
David, it's great to read about all the new features coming. Not since Excel 97 have we seen such an effort. Thanks! Are there any improvements to analysis features such as Scenario Manager, Solver, Goal Seek or Data Input Tables? Any new what-if features? Also, will VBA inherit any VB.NET characteristics?
Regards,
Colin
Exciting stuff, David.
Jim
Excel MVP
(not at summit)
XL-Dennis – We have not done anything specific to ADO.NET in Excel 12, but using Visual Studio 2005 Tools for Office you can databind a named range to a DataSet, DataTable, DataView, or anything that implements IList, IListSource, BindingList etc. This VSTO 2005 tool support is based on standard VS tools for databinding. That means, at design-time (with a few button clicks) you can very easily databind a named range or list to a database/table(s), stored procedure, web service, or any arbitrary business object that implements any of the specified interfaces.
Also, the new functions that return data from SQL Server Analysis Services will also work with SQL AS 2000.
Rob – yes, we will support multiple CPUs. More in a later post. Also, starting next week I will write several articles on conditional formatting, so I will try and answer questions there. I will have a post on new functions in the not-too-distant future too. Thanks for the interest!
Pete – One of the key reasons we are doing user interface work this release is to make it easier for people to find and use the features and commands they need to get the results they want. There is an overview here. www.microsoft.com/.../uioverview.mspx Our hope is that this leads to much greater feature use.
Colin – No changes to S Manager, Goal Seek, Solver, or Data Tables this time out.
Rob van Gelder...
...
>hardware>
>Does this mean that the calculation engine >will support multiple CPUs?
Also, does it mean fully using hardware floating point units? Clearly Excel's MOD function doesn't since
MOD(2^30,3)
returns a #NUM! error even though that particular calculation is well within IEEE bounds and Intel FPUs' have no trouble with it.
>Could you please reveal some of the new >function names available?
It'd be nice to see what the new functions are. Certainly there's room for improvement in the text handling functions, but Excel isn't really meant for text processing.
Of all the things that could be added, the two that would be the most useful would be adding built-in regular expression support to Excel (just like in OpenOffice) and making 3D references part of Excel's object model so they could be passed to VBA functions. The former would make a LOT of the long & complex text formulas offerred in the newsgroups unnecessary, and the latter would allow 3D references to udfs [note that the NPV function *already* handles 3D references in 2nd and subsequent args, and it's order-dependent, so there should already be an iterator for 3D references that could be used in For Each loops].
>Colin No changes to S Manager, Goal Seek, Solver, or Data Tables this time out.
A nice feature that would be fairly quick to build.
Currently, I dont know how to submit to Microsoft a feature request.
In the Help menu, "Suggest a feature"
or "Wishlist"?
Thanks,
Rob
This is shaping up to be the first seriously compelling version of Excel since 97. It'll probably wear off while we wait () but I'm seeing enough to make me plan for an immediate upgrade, rather than "when I get round to it" as in the previous 3 or 4 releases...
Cool. Very cool. Of course it'll be about a decade for any of my likely workplaces consider rolling it out because it'll be new, different and therefore scary.
Regarding the enhancements associated with SQL Server, what is the nature of the connectivity? Will it work will other databases? Many more people use Excel with other databases than use Excel with SQL Server.
Great news! In particular, I'm excited about the conditional formatting and charting enhancements!
Two requests (and like Colin, I completely understand if Excel 12 is long since closed to changes):
1) Variable width column charts. It's possible to fake these with the area- and stacked-area- charts, but it's really painful to make them that way.
2) Weighted linear regression formulae. I can make a bubble chart already, with (x, y, size) data points. I can add a trendline to that chart, but the trendline's based solely on the (x,y) points - it pays no attention to size. Conceptually, the next step would be a weighted linear regression, where each data point's repeated (size) times in the summations. [I tried doing this by hand - not sure if it's computationally prohibitive or if it's easy to optimize]
Thanks!
Any chance of offering a TSQL-like query language for looking up values? I usually spend far too long messing with VLOOKUP when a simple "select [column_a] from [range] where [column_b]=[value]" would be infinitely easier.
Greetings,
Rob – Details when I get to those posts, I promise. Thanks for the feedback on functions & 3-D referencing. Also, feature requests can be sent to xlwish@microsoft.com, or you can just put them in comments to this blog.
Colin – Thanks for the feedback on Scenario Manager. I will cover undo in a later post, but the short answer is no, you will not be limited to 16.
mm – The connectivity enhancements will work with any sort of connection – OLEDB, ODBC, etc. – so they will not be limited to SQL Server.
Jason – Thanks for the feedback.
Brooks – Thanks for the feedback. While we have not done exactly that, we have done some referencing work that may help a lot. More in a few weeks.
Good morning, found this via a link @ Arstechnica.
I am certainly no expert when it comes to Excel, but I was trying to create a graph with a broken Y axis the other day. After searching around the 'net I saw that there was not much chance of me figuring it out since it was quite a convoluted solution.
Any chance that will be incorporated into your changes for v12?
And thanks for the many other changes I have seen, mostly in regards to lifting some of the row limits. I can't wait for this to get qualified by our IT security... :)
Comments: (loading) Collapse