S
smithkl42
As I've read about the Excel 2007 performance improvements that MS
touts in Excel 2007
(http://msdn2.microsoft.com/en-us/library/aa730921.aspx, for instance),
I've had to refrain from laughing out loud. For all I know, MS
actually has managed to improve the calculation engine in 2007 -- but I
wouldn't know, because for all the huge worksheets that I've built and
worked with over the years, I've never had recalculation be the
bottleneck. What I do know is that for the typical user in our
organization, Excel 2007 is at least an order of magnitude slower than
Excel 2003.
To take just one example: we've built a reasonably complex spreadsheet
using a combination of VBA and external data access that pulls data
from a couple of tables on a SQL server, and displays ~50 graphs spread
out over 8 tabs. On a variety of machines running Excel 2003, it takes
approximately one second to re-select the data from the SQL table and
refresh those 50 graphs; and of course, navigating between tabs, and
scrolling up and down within tabs is as speedy as we're all used to.
The same spreadsheet, moved to Excel 2007, takes between 5-15 seconds
to refresh (depending on the machine), and you can actually watch the
graphs repainting themselves on the screen. And scrolling up and down
within a tab, as new graphs come on the screen and leave, is so slow
and clunky as to make it almost unusable. (Oh, and it also leaves
fragments of graphs sitting on your screen as the previous graphs
leave.)
MS apparently made the switch to a common charting engine across Office
2007, and screwed their users in the process. Entirely apart from the
ribbon interface (which I hate -- try doing a paste special in Outlook
from the keyboard), it's performance that is going to keep our company
from migrating to Office 2007.
Just wanted to post my annoyance and frustration somewhere. I'm a big
MS fan -- and I desperately hope that MS fixes the performance issues
in a service pack, and soon.
Ken
touts in Excel 2007
(http://msdn2.microsoft.com/en-us/library/aa730921.aspx, for instance),
I've had to refrain from laughing out loud. For all I know, MS
actually has managed to improve the calculation engine in 2007 -- but I
wouldn't know, because for all the huge worksheets that I've built and
worked with over the years, I've never had recalculation be the
bottleneck. What I do know is that for the typical user in our
organization, Excel 2007 is at least an order of magnitude slower than
Excel 2003.
To take just one example: we've built a reasonably complex spreadsheet
using a combination of VBA and external data access that pulls data
from a couple of tables on a SQL server, and displays ~50 graphs spread
out over 8 tabs. On a variety of machines running Excel 2003, it takes
approximately one second to re-select the data from the SQL table and
refresh those 50 graphs; and of course, navigating between tabs, and
scrolling up and down within tabs is as speedy as we're all used to.
The same spreadsheet, moved to Excel 2007, takes between 5-15 seconds
to refresh (depending on the machine), and you can actually watch the
graphs repainting themselves on the screen. And scrolling up and down
within a tab, as new graphs come on the screen and leave, is so slow
and clunky as to make it almost unusable. (Oh, and it also leaves
fragments of graphs sitting on your screen as the previous graphs
leave.)
MS apparently made the switch to a common charting engine across Office
2007, and screwed their users in the process. Entirely apart from the
ribbon interface (which I hate -- try doing a paste special in Outlook
from the keyboard), it's performance that is going to keep our company
from migrating to Office 2007.
Just wanted to post my annoyance and frustration somewhere. I'm a big
MS fan -- and I desperately hope that MS fixes the performance issues
in a service pack, and soon.
Ken