How can VBA code which executes in under one second in Excel 2003 turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming

i asked the same thing a while back, here's the post:

i am just curious if anyone sees a substantial degradation of speed when using
vistax64/2007 vs xp/2003.

i was on the beta for both vista and office 2007, and refuse to use either.

i dual boot. when i run an app under vistax64/2007, it takes 4 seconds to
complete, while under xp/2003 it's maybe a second. i know it doesn't seem like
much, but everything i run is slower. this particular app loads and closes about
10 workbooks while it populates a schedule and does some other things. i
personally think they're both useless and i'm glad i got them for free.

someday when i feel like punishing myself, i'll install my 32 bit version of
vista and see if it's any better

--


Gary


"Peter Acton" wrote in message
...
How can VBA code which executes in under one second in Excel 2003 turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming

Hi Peter,

If you'd like some assistance from folks on here then why not post your code
and describe the problem, perhaps indicating what you have tried already.
Alternatively, just post a one off rant and blame Bill Gates for everything.




--
www.alignment-systems.com


"Peter Acton" wrote:

How can VBA code which executes in under one second in Excel 2003 turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming

It's probably not the code, John. Many people have reported performance
degradation in Excel 2007, from moderate to severe. And I don't see a rant
in Peter's post. I think customers have a right to be _very_ disappointed
and express it.

--
Jim
"John.Greenan" wrote in message
...
| Hi Peter,
|
| If you'd like some assistance from folks on here then why not post your
code
| and describe the problem, perhaps indicating what you have tried already.
| Alternatively, just post a one off rant and blame Bill Gates for
everything.
|
|
|
|
| --
| www.alignment-systems.com
|
|
| "Peter Acton" wrote:
|
| How can VBA code which executes in under one second in Excel 2003 turn
into a
| marathon 62 seconds in Excel 2007?
|
| ----------------
| This post is a suggestion for Microsoft, and Microsoft responds to the
| suggestions with the most votes. To vote for this suggestion, click the
"I
| Agree" button in the message pane. If you do not see the button, follow
this
| link to open the suggestion in the Microsoft Web-based Newsreader and
then
| click "I Agree" in the message pane.
|
|
http://www.microsoft.com/office/comm...el.programming

Hi Jim.

Indeed many people have reported problems with 2007 - I reported a few when
I was beta testing Excel 2007.

Here's my point though - why doesn't the poster describe what the problem
is and give an example of this and maybe get in touch with David Gainer at
Microsoft - you can contact him via his blog at http://blogs.msdn.com/excel/

Along with a lot of folks on this newsgroup I try and help people with
problems - you can type my surname into the search facility and see that I
answer a lot of questions about real time data such a s Bloomberg and Reuters
and using this with Excel.

Do folks think Bill Gates will read a newsgroup posting and then say "Stop
everything - here's an unspecified performance issue with something to do
with Excel 2007". No, but if you actually engage with Microsoft in a
sensible way - list the problem and so on, you will find that they will
usually respond.

I don't work for Microsoft and I often criticise them but do so in a manner
that says "here's a specific problem, here's why it's a problem and here's a
few ideas about this" and you know what - Microsoft do listen. They have
what - 500 million users (maybe more - I don't know) so they cannot simply
drop everything and respond to every unstructured complaint.

Raise the issue in a sensible way, show that you have researched it and then
be part of the solution, not sitting on the touchline complaining.


--
http://www.alignment-systems.com


"Jim Rech" wrote:

It's probably not the code, John. Many people have reported performance
degradation in Excel 2007, from moderate to severe. And I don't see a rant
in Peter's post. I think customers have a right to be _very_ disappointed
and express it.

--
Jim
"John.Greenan" wrote in message
...
| Hi Peter,
|
| If you'd like some assistance from folks on here then why not post your
code
| and describe the problem, perhaps indicating what you have tried already.
| Alternatively, just post a one off rant and blame Bill Gates for
everything.
|
|
|
|
| --
| www.alignment-systems.com
|
|
| "Peter Acton" wrote:
|
| How can VBA code which executes in under one second in Excel 2003 turn
into a
| marathon 62 seconds in Excel 2007?
|
| ----------------
| This post is a suggestion for Microsoft, and Microsoft responds to the
| suggestions with the most votes. To vote for this suggestion, click the
"I
| Agree" button in the message pane. If you do not see the button, follow
this
| link to open the suggestion in the Microsoft Web-based Newsreader and
then
| click "I Agree" in the message pane.
|
|
http://www.microsoft.com/office/comm...el.programming

John-

I don't care for Bill Gates bashing or "M$" and all that either, but Peter
didn't do any of that. He just let out a primordial scream. Your points are
all valid, I just think you should have saved them for a poster who merited
them.<g

As for XL2007 performance issues, MS is surely aware of them and I imagine
has all the example it needs. If not it can ask via Dave's blog as it did
for PivotTable examples in April.

--
Jim
"John.Greenan" wrote in message
...
| Hi Jim.
|
| Indeed many people have reported problems with 2007 - I reported a few
when
| I was beta testing Excel 2007.
|
| Here's my point though - why doesn't the poster describe what the problem
| is and give an example of this and maybe get in touch with David Gainer at
| Microsoft - you can contact him via his blog at
http://blogs.msdn.com/excel/
|
| Along with a lot of folks on this newsgroup I try and help people with
| problems - you can type my surname into the search facility and see that I
| answer a lot of questions about real time data such a s Bloomberg and
Reuters
| and using this with Excel.
|
| Do folks think Bill Gates will read a newsgroup posting and then say "Stop
| everything - here's an unspecified performance issue with something to do
| with Excel 2007". No, but if you actually engage with Microsoft in a
| sensible way - list the problem and so on, you will find that they will
| usually respond.
|
| I don't work for Microsoft and I often criticise them but do so in a
manner
| that says "here's a specific problem, here's why it's a problem and here's
a
| few ideas about this" and you know what - Microsoft do listen. They have
| what - 500 million users (maybe more - I don't know) so they cannot simply
| drop everything and respond to every unstructured complaint.
|
| Raise the issue in a sensible way, show that you have researched it and
then
| be part of the solution, not sitting on the touchline complaining.
|
|
| --
| http://www.alignment-systems.com
|
|
| "Jim Rech" wrote:
|
| It's probably not the code, John. Many people have reported performance
| degradation in Excel 2007, from moderate to severe. And I don't see a
rant
| in Peter's post. I think customers have a right to be _very_
disappointed
| and express it.
|
| --
| Jim
| "John.Greenan" wrote in message
| ...
| | Hi Peter,
| |
| | If you'd like some assistance from folks on here then why not post
your
| code
| | and describe the problem, perhaps indicating what you have tried
already.
| | Alternatively, just post a one off rant and blame Bill Gates for
| everything.
| |
| |
| |
| |
| | --
| | www.alignment-systems.com
| |
| |
| | "Peter Acton" wrote:
| |
| | How can VBA code which executes in under one second in Excel 2003
turn
| into a
| | marathon 62 seconds in Excel 2007?
| |
| | ----------------
| | This post is a suggestion for Microsoft, and Microsoft responds to
the
| | suggestions with the most votes. To vote for this suggestion, click
the
| "I
| | Agree" button in the message pane. If you do not see the button,
follow
| this
| | link to open the suggestion in the Microsoft Web-based Newsreader
and
| then
| | click "I Agree" in the message pane.
| |
| |
|
http://www.microsoft.com/office/comm...el.programming
|
|
|

For people who are inclined to be beta testers, that's very sensible
advice.

For those who expect performance from a product that they paid a lot of
money for, based on marketing hype from MS along with a rather
reasonable assumption that performance on an upgraded product shouldn't
be significantly worse than what they had, I don't agree at all.

Most people have to *work*, not do free research on MS's behalf.




In article ,
John.Greenan wrote:

Raise the issue in a sensible way, show that you have researched it and then
be part of the solution, not sitting on the touchline complaining.

Seems to me that you are saying that you believe marketing hype. In which
case perhaps a newsgroup for developers is not the best place for you?

--
http://www.alignment-systems.com


"JE McGimpsey" wrote:

For people who are inclined to be beta testers, that's very sensible
advice.

For those who expect performance from a product that they paid a lot of
money for, based on marketing hype from MS along with a rather
reasonable assumption that performance on an upgraded product shouldn't
be significantly worse than what they had, I don't agree at all.

Most people have to *work*, not do free research on MS's behalf.




In article ,
John.Greenan wrote:

Raise the issue in a sensible way, show that you have researched it and then
be part of the solution, not sitting on the touchline complaining.

Can I be a beta tester?



"John.Greenan" wrote:

Seems to me that you are saying that you believe marketing hype. In which
case perhaps a newsgroup for developers is not the best place for you?

--
http://www.alignment-systems.com


"JE McGimpsey" wrote:

For people who are inclined to be beta testers, that's very sensible
advice.

For those who expect performance from a product that they paid a lot of
money for, based on marketing hype from MS along with a rather
reasonable assumption that performance on an upgraded product shouldn't
be significantly worse than what they had, I don't agree at all.

Most people have to *work*, not do free research on MS's behalf.




In article ,
John.Greenan wrote:

Raise the issue in a sensible way, show that you have researched it and then
be part of the solution, not sitting on the touchline complaining.

No, I'm not saying that at all. I don't believe any of the hype (I use
WinOffice only sparingly for compatibility purposes). But I know that
most of my larger clients who have decided to upgrade do (and MS
wouldn't waste their $10Ms in advertising if they didn't). Their
employees are then left in the unfortunate position of having to deal
with that decision.

Of course, the instant issue really has nothing to do with the hype.
Even unhyped, users have a reasonable expectation that their macros
won't experience a 3000% increase in execution time after an upgrade.

OTOH, this is hardly a "newsgroup for developers" any longer. It's
accessed by everyone from novices to experts, many (if not most) of whom
are dumped here by a variety of web interfaces that present a largely
inscrutable hierarchy (the Mac Office groups appear first on the list on
one MS site, so they regularly get 50% WinOffice-specific questions).
Since you don't post very regularly, you may not have noticed.

And again, even if it WERE a newsgroup solely for developers, and even
if there were NO hype, there's NO reason I can think of why a developer
customer should consent to do post-beta testing for MS on their own
dime, after paying a significant sum for a relatively mature product.
The product should work.

MS, like other software manufacturers, is lucky that there are those of
us who do it for free.

In article ,
John.Greenan wrote:

Seems to me that you are saying that you believe marketing hype. In which
case perhaps a newsgroup for developers is not the best place for you?

--
http://www.alignment-systems.com


"JE McGimpsey" wrote:

For people who are inclined to be beta testers, that's very sensible
advice.

For those who expect performance from a product that they paid a lot of
money for, based on marketing hype from MS along with a rather
reasonable assumption that performance on an upgraded product shouldn't
be significantly worse than what they had, I don't agree at all.

Most people have to *work*, not do free research on MS's behalf.

Hi John

Thanks for your very kind offer but I didn't have the time to resolve this
issue so I reverted back to Excel 2003.

The problem is caused by the treatment of CSV files using Excel 2007. My
code opens a CSV file and then strips rows according to some logic.

The degradation in performance is due to the fact that the code was using
End Down on a blank column. This is acceptable in Excel 2003 whilst
addressing 65536 rows but causes a considerable degradation in performance in
Excel 2007 which utilises the 1048576 row worksheet.

I did contact Microsoft support on this issue and sent the consultant my
code but quite frankly I found this to be a complete waste of time, hence my
exasperated posting.

As an example, when I logged my incident, the IE software downloaded an
exhaustive listing of my hardware and software versions and settings. The
consultant then e-mailed me and the first thing he asked for was for me to
e-mail him a listing of my hardware and software versions and settings.

So there you go; I raised the issue in a sensible way, I showed that I had
researched the issue and I was part of the solution.


"John.Greenan" wrote:

Hi Peter,

If you'd like some assistance from folks on here then why not post your code
and describe the problem, perhaps indicating what you have tried already.
Alternatively, just post a one off rant and blame Bill Gates for everything.




--
www.alignment-systems.com


"Peter Acton" wrote:

How can VBA code which executes in under one second in Excel 2003 turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming

I have an app that generates about 100 large spreadsheets. When I installed
2007 on a Vista machine, the performance of the app was appalling
(2003=50secs, 2007 over 5 minutes). The strange thing was that the CPU was
only at a low level, when it usually is high. For some reason I put the
Office 2007 DVD back it and told it to do a repair. The problem disappeared.
There is still a performace issue though - 50 secs on 2003 and 165 on 2007.
This means that a run of 1.5 hours will take over 5 hours to complete on 2007.
--
John Austin


"Peter Acton" wrote:

Hi John

Thanks for your very kind offer but I didn't have the time to resolve this
issue so I reverted back to Excel 2003.

The problem is caused by the treatment of CSV files using Excel 2007. My
code opens a CSV file and then strips rows according to some logic.

The degradation in performance is due to the fact that the code was using
End Down on a blank column. This is acceptable in Excel 2003 whilst
addressing 65536 rows but causes a considerable degradation in performance in
Excel 2007 which utilises the 1048576 row worksheet.

I did contact Microsoft support on this issue and sent the consultant my
code but quite frankly I found this to be a complete waste of time, hence my
exasperated posting.

As an example, when I logged my incident, the IE software downloaded an
exhaustive listing of my hardware and software versions and settings. The
consultant then e-mailed me and the first thing he asked for was for me to
e-mail him a listing of my hardware and software versions and settings.

So there you go; I raised the issue in a sensible way, I showed that I had
researched the issue and I was part of the solution.


"John.Greenan" wrote:

Hi Peter,

If you'd like some assistance from folks on here then why not post your code
and describe the problem, perhaps indicating what you have tried already.
Alternatively, just post a one off rant and blame Bill Gates for everything.




--
www.alignment-systems.com


"Peter Acton" wrote:

How can VBA code which executes in under one second in Excel 2003 turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming

Make sure you have removed the Google Office Com Addin: it slows down excel
significantly and 2007 suffers even more.

May also be worth trying 2007 SP1, it does speed up some things so might
help

regards
Charles
_________________________________________
FastExcel 2.3
Name Manager 4.0
http://www.DecisionModels.com

"John Austin" wrote in message
...
I have an app that generates about 100 large spreadsheets. When I installed
2007 on a Vista machine, the performance of the app was appalling
(2003=50secs, 2007 over 5 minutes). The strange thing was that the CPU was
only at a low level, when it usually is high. For some reason I put the
Office 2007 DVD back it and told it to do a repair. The problem
disappeared.
There is still a performace issue though - 50 secs on 2003 and 165 on
2007.
This means that a run of 1.5 hours will take over 5 hours to complete on
2007.
--
John Austin


"Peter Acton" wrote:

Hi John

Thanks for your very kind offer but I didn't have the time to resolve
this
issue so I reverted back to Excel 2003.

The problem is caused by the treatment of CSV files using Excel 2007. My
code opens a CSV file and then strips rows according to some logic.

The degradation in performance is due to the fact that the code was using
End Down on a blank column. This is acceptable in Excel 2003 whilst
addressing 65536 rows but causes a considerable degradation in
performance in
Excel 2007 which utilises the 1048576 row worksheet.

I did contact Microsoft support on this issue and sent the consultant my
code but quite frankly I found this to be a complete waste of time, hence
my
exasperated posting.

As an example, when I logged my incident, the IE software downloaded an
exhaustive listing of my hardware and software versions and settings. The
consultant then e-mailed me and the first thing he asked for was for me
to
e-mail him a listing of my hardware and software versions and settings.

So there you go; I raised the issue in a sensible way, I showed that I
had
researched the issue and I was part of the solution.


"John.Greenan" wrote:

Hi Peter,

If you'd like some assistance from folks on here then why not post your
code
and describe the problem, perhaps indicating what you have tried
already.
Alternatively, just post a one off rant and blame Bill Gates for
everything.




--
www.alignment-systems.com


"Peter Acton" wrote:

How can VBA code which executes in under one second in Excel 2003
turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to
the
suggestions with the most votes. To vote for this suggestion, click
the "I
Agree" button in the message pane. If you do not see the button,
follow this
link to open the suggestion in the Microsoft Web-based Newsreader and
then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming

Thanks, will do.
--
John Austin


"Charles Williams" wrote:

Make sure you have removed the Google Office Com Addin: it slows down excel
significantly and 2007 suffers even more.

May also be worth trying 2007 SP1, it does speed up some things so might
help

regards
Charles
_________________________________________
FastExcel 2.3
Name Manager 4.0
http://www.DecisionModels.com

"John Austin" wrote in message
...
I have an app that generates about 100 large spreadsheets. When I installed
2007 on a Vista machine, the performance of the app was appalling
(2003=50secs, 2007 over 5 minutes). The strange thing was that the CPU was
only at a low level, when it usually is high. For some reason I put the
Office 2007 DVD back it and told it to do a repair. The problem
disappeared.
There is still a performace issue though - 50 secs on 2003 and 165 on
2007.
This means that a run of 1.5 hours will take over 5 hours to complete on
2007.
--
John Austin


"Peter Acton" wrote:

Hi John

Thanks for your very kind offer but I didn't have the time to resolve
this
issue so I reverted back to Excel 2003.

The problem is caused by the treatment of CSV files using Excel 2007. My
code opens a CSV file and then strips rows according to some logic.

The degradation in performance is due to the fact that the code was using
End Down on a blank column. This is acceptable in Excel 2003 whilst
addressing 65536 rows but causes a considerable degradation in
performance in
Excel 2007 which utilises the 1048576 row worksheet.

I did contact Microsoft support on this issue and sent the consultant my
code but quite frankly I found this to be a complete waste of time, hence
my
exasperated posting.

As an example, when I logged my incident, the IE software downloaded an
exhaustive listing of my hardware and software versions and settings. The
consultant then e-mailed me and the first thing he asked for was for me
to
e-mail him a listing of my hardware and software versions and settings.

So there you go; I raised the issue in a sensible way, I showed that I
had
researched the issue and I was part of the solution.


"John.Greenan" wrote:

Hi Peter,

If you'd like some assistance from folks on here then why not post your
code
and describe the problem, perhaps indicating what you have tried
already.
Alternatively, just post a one off rant and blame Bill Gates for
everything.




--
www.alignment-systems.com


"Peter Acton" wrote:

How can VBA code which executes in under one second in Excel 2003
turn into a
marathon 62 seconds in Excel 2007?

----------------
This post is a suggestion for Microsoft, and Microsoft responds to
the
suggestions with the most votes. To vote for this suggestion, click
the "I
Agree" button in the message pane. If you do not see the button,
follow this
link to open the suggestion in the Microsoft Web-based Newsreader and
then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming