It's not that the
VB runs slower - my ad hoc 'tests' are inconclusive on
that. It's the charting engine that is the giant killer. Quite frankly, the
client I was working with went back to 2003 after we discovered all of this
(and he'd already spent the money for 2007 at my recommendation - I felt
really bad about that). In his case, he had data files approaching 1/2
million lines of code and wanted to pull it all in and, like you, divide it
up into groups and chart it and we thought this would be an excellent
opportunity/reason to go to Excel 2007 with its 2^20 rows ability. That side
of things worked as advertised - then we started graphing it...
"JohnJohn" wrote:
To answer Tim's question: The Visual Basic code breaks down a column of 10k
integers into subgroups of the numbers and then does statistical comparisons
of the subgroups with a reference area on a sheet.
To reply to Jlatham: yes, the code - does - create 8-12 charts, each of
which can have up to 10k data points. So maybe, what you suggest (charting)
is the problem.
Today, I purchased a new Toshiba laptop with 2 gig memory and an Intel
Pentium dual core T2060 processor with Office 2007 and Vista Home Premium. On
the new laptop, the code that runs on my old laptop with an Intel Celeron M
380 processor and 512 meg. ram, Win XP and Office 2002 in 2 minutes, still
takes 3 min. and 50 seconds to run on the new laptop in the Office 2007.
Without trying to be a wiseguy, if this is the case with Office 2007,
running Visual Basic code - slower - the Office 2002, then I'm astonished. Am
I missing something here. Why would a programmer upgrade?
John
"JLatham" wrote:
Tim Williams has asked a key question: what does your code do?
I've found that Excel 2007 generally performs as fast as 2003 for most
operations; sometimes a bit slower, sometimes a bit faster, but any
difference was almost negligable, UNLESS I was dealing with
charting/graphing or graphic objects. At that point 2007 suffers serious
slowdowns. It's a known issue and MSFT is working on making it better.
Example: I have an application that graphs 8800 data points in an X-Y
scattercharts (51 charts in all). In Excel 2003 (on an older single core
system with 1GB RAM) the whole process takes about 2.5 minutes to read the
data (actually 1/2 million rows of it from a .txt file) and then create the
graphs. The same process in Excel 2007 takes about 12 minutes.
"JohnJohn" wrote:
I have a Visual Basic procedure in the Excel of my Microsoft Office 2003 that
I've run hundreds of times and it finishes in 2 minutes.
Yesterday, I installed my new Microsoft Office Home & Student 2007 on the
same computer (and told it to remove the old Office) and it installed with no
errors or problems. But when I ran the same Visual Basic procedure that took
2 minutes to complete in my old Office 2003, now in the new Office 2007,
Excel, it took 6 and a half minutes to finish (with no errors).
The computer is a Toshiba laptop with 512 meg memory, 100 gig hard drive and
Windows XP Professional and is only a year old.
Could someone what's wrong. Why does the identical VB code take so much
longer to run.
Thanks ...
John