Thanks for all the info. I knew there was a BIG problem but you have to
look for it on the internet. I know lots of people who've experienced
this slowdown firsthand so I'm surprised how little is out there.
Conspiracy? :o)

As an experiment I ran a spreadsheet macro in '03 and '07. 2003 ran the
macro in 18 sec, 2007 (w/ 4 x 3.2GHz processors) ran it in 2:33. When I
manually set the # of processors to just 1 it actually sped up the run
time by 4 sec.

I hope MS doesn't try to fool people into thinking this is a hardware
issue. My workstation is very fast, with all the latest updates, 4 GB
RAM, no junk programs running in the background. I run my box as lean
and mean as I can.

That's why I had to "upgrade" back to Office XP today. Couldn't handle
it anymore.




*** Sent via Developersdex http://www.developersdex.com ***

It's now January 2008, and I notice this thread goes back to mid-2007,
without any (apparent) fix by MS. Someone indicated earlier that very
few people use large numbers of rows or columns -- I definitely do, and
that's why I "graduated" to Office 2007. I thought that the interface
between Access and Excel would be much cleaner when both could handle
the 1/2 Million or so rows I generally have in my files. Excel is
incredibly slow even in the simplest activities (I just waited 20
minutes to clear a couple of columns in a 70,000 row spreadsheet).
Inserting blank columns takes forever, even when there are no formulas
in the spreadsheet (I remove the formulas by paste special/values, just
because they slow things down so much).
It seems as if the programs (both Access and Excel) are "anticipating"
what a user might do, and pre-storing or pre-computing stuff --
otherwise, why would a simple column insertion or deletion take so much
time?
I didn't know about being able to save the old Office version when I
installed, so I either have to wait for a real fix from MS, or get on
another computer with Office 2003. Is this what happens when you have a
total monopoly in this product area?


*** Sent via Developersdex http://www.developersdex.com ***

I followed some of the recommendations described he

http://msdn2.microsoft.com/en-us/library/aa730921.aspx

like making calculations manual and using both ptocessors, but Excel is
still painfully slow. SP1 did noy help. My worksheet is only 500 rows
by 14 columns. The same worksheet works fast in Excel 2003.

*** Sent via Developersdex http://www.developersdex.com ***

The solution described here worked!

http://www.eggheadcafe.com/software/...xcel-2007-calc
ulati.aspx


*** Sent via Developersdex http://www.developersdex.com ***