PDA

View Full Version : Excel 2007 - warning about an issue thats been plaguing me


fivecheebs
26th March 2009, 15:33
Hi guys,

I just wanted to warn everyone about an issue that has caused me a few headaches this week.

I have been busy for the last few days preparing a financial model for a proposed property purchase by the company I work for. Its a very large workbook consisting of over 40 sheets. Excel seemed to be replacing some formulae with #N/A. Particularly, in my case, date formulae. The sheet seemed fine until something happened, and I'm not sure what. It could have been the file size, butt his is guesswork, as the workbook was weighing in at 25Mb or more. I was using compatibility mode (saves the file as .xls rather than the new default of .xlsx) for obvious reasons, and this seemed to be the cause.

In my case it took me 2.5 days initially to get the raw data in the predefined model. The issue does not show itself until after you re-open the workbook after its been saved and closed. Its taken me another 2 days to fix and figure out what the problem was.

So, If you need to create a very large workbook in Excel 2007, then please use the native file type, .xlsx, to save lots of re-working that I have had to do over the last few days.

fillip
26th March 2009, 22:10
I refuse to use Office 2007 as they've twatted about with it too much - moving certain settings to different locations, changing menu layouts. Plus it just looks bulky and rubbish. Slows my system down a fair bit as well so I'm hanging on to 2003 for now.

Thanks though, may well crop up during support work at some point. :thumb:

jaguarking11
27th March 2009, 07:18
Same here, I continue to use the 2003 office suite. There is only so much you can add to office suite anyway. Gets my work done just fine.

zittware
1st April 2009, 08:12
funny thing is I heard a rumor somewhere...
Microshaft will optimize Winders for a specific CPU to squeze as much perf out of a device as it can.
However, Office they do everthing in generic CPU instructions and non-opmizing compilers... as they want it to be portable and "just work".
Might explain why Office is so damn slow on modern machines.