Macro slow (worked well until I upgraded my machine)

[Epidemic]

I am doing an iterative hide of columns that of all but ones which meet the
day of the week criteria. The macro ran fine for years through the upgrade
from 2003 to office 2007.

I have just upgraded my machine to a more powerful machine and my macro now
takes has increased processing time by 50 to 60 times for this iterative hide.

I have noticed that machines that went through the office 2003 installation
prior to 2007 still run it fine.

Example dell latitude d620 that never had 2003 takes 2 to 3 minutes to
complete. same type of laptop that did go through the path takes
approximately 2 seconds on a slow day.

finally my dual core optiplex 760 with 3 gig or ram takes several minutes.

outside of installing office 2003 on dozens of machines and then upgrading
to 2007 is there a solution?

 

[ker_01]

One thing I'd check (and maybe the experts can chime in on whether this
actually affects processing time to the extent you are describing); on your
upgraded machine, is XL07 running in "compatibility mode"? Create a new
worksheet on both machines, and scroll to the right to see the last column.
If it is IV on the upgraded machine, but in the triple digits for the regular
2007 machines, that might be part of the problem depending on how you set up
your code (e.g. does it check columns 1-100 or does it check "each column in
columns").

Either way, Barb's suggestion is a good one. Also, do you turn of
calculation and screenupdating at the top of your code block, and turn them
back on at the bottom?

HTH,
Keith

 

[Epidemic]

My question is not so much can I recode it. My question is what library, or
utility or feature gets turned on when I install 2003 and subsequently 2007
which allows the excel to work correctly. Yes I can read everything into an
array and or name a range and then hide it. The question is what changed?


I see hundreds of posts about the speed being reduced and people having to
rewrite things. does anyone know what the sollution to this is. the
code is apparantly already available. Microsoft just needs to tell us the
application/library/addin to load to make it work like it used to.

does anyone have any clue how to accomplish this?


Microsoft do you have anyclue what is causing this?

 

[Epidemic]

Crap I meant to hit no. This did not answer my question.


my macro is running on identical machines with modes set the same exact file
and version of 2007. with options set (at least in theory). the only
difference is that one was upgraded from 2003 and one was a complete new
install from os on to 2007 with no 2003

the 2003 upgrade path to 2007 wins the race by miles every time.