On 02/06/2010 15:20, Daniel Piestrak wrote:
Did you ever find a solution?

I have users across my office expierencing this issue as well.

I have tried the methods you posted above with also no success.

Greg Lovern wrote:

A user has now reported the problem while using the workbook on whichI had
16-Feb-08

A user has now reported the problem while using the workbook on which
I had done the corruption repair.

To test whether the problem was caused by heavy cpu usage per the
other poster, I tried a freeware utility called "Obrut" (turbo spelled
backward), which applies heavy cpu usage and also heavy memory usage.
But even with Obrut on maximum, which slowed my computer down quite a
bit, I still couldn't get a repro.

All of the affected users are on Excel 2007 without service pack, and
the organization has recently approved Office 2007 SP1, so next step
is that we're having affected users install SP1. It may be a few weeks
before we really know whether SP1 helps.

Any other suggestions?

If they are still using XL2007 without sp2 it is amazing they can get
any useful work done at all. The original out of the box version was
unstable wrt race conditions on some multicore machines. Graphics and
charting in combination with VBA would elicit some interesting faults.
Talking here of stable working XL2003 code.

It is still horribly slow at charts and graphics even now and I have a
couple of spreadsheets that use solver and can be killed stone dead by a
too impatient double click on a cell. At least you don't lose any data
but the crashing behaviour in XL2007 is less than ideal.

Regards,
Martin Brown