![]() |
Excel 2007 Disappointment
I have been very disappointed in what I've seen of Excel 2007. I have
numerous worksheets that are very important, and I've been doing nothing for days but recovering them, trying to convert them, and waiting on them to save to disk. Obviously it has been extremely unproductive. I have converted from Excel 2003 a workbook that has less than 10 worksheets, all with lists, has protected sheets, it is modified every time it opens because it uses random number generation, and has a password access. I have run it under compatibility mode and also converted it to native mode. I can almost never open it access other applications, and return to it that it doesn't have to be autorecovered. When I finally save it, I really wonder what's been lost. I have another very important workbook that contains in excess of 100 worksheets. It is the front end of a VBA application. Again, I have run it in compatibility mode, and also converted it to the macro enabled mode. It's almost impossible to just save it. It again is constantly being autorecovered. I've changed autosave to 30 minutes, because Excel shows as not responding, however in the Task manager, I can see it's probably doing an autosave, and CPU performance is around 50% for the process. I have noticed that the native file size is significantly smaller, but the time to load or save is significantly longer. I would trade time for disk space anyday. Any suggestions? I'm leary of converting any other work, and seriously considering returning to Excel 2003. Surely these types of things showed up prior to release. Is there a bug list or problem list that is available for the product? Any help would be appreciated. -- Ross |
Excel 2007 Disappointment
Ross
Excel 2007 has some faults (?) but I am happily running 2003 and 2007 on two or three machines with no trouble (little) I would look at your personal.xls, excel.xlb and any add-ins or start-up templates you have loaded and consider temporarily taking them away to see if issues clear up. Mine was a clean install on a clean machine as I had so much garbage from the betas (Both XP and Vista) -- HTH Nick Hodge Microsoft MVP - Excel Southampton, England DTHIS www.nickhodge.co.uk "RossR" wrote in message ... I have been very disappointed in what I've seen of Excel 2007. I have numerous worksheets that are very important, and I've been doing nothing for days but recovering them, trying to convert them, and waiting on them to save to disk. Obviously it has been extremely unproductive. I have converted from Excel 2003 a workbook that has less than 10 worksheets, all with lists, has protected sheets, it is modified every time it opens because it uses random number generation, and has a password access. I have run it under compatibility mode and also converted it to native mode. I can almost never open it access other applications, and return to it that it doesn't have to be autorecovered. When I finally save it, I really wonder what's been lost. I have another very important workbook that contains in excess of 100 worksheets. It is the front end of a VBA application. Again, I have run it in compatibility mode, and also converted it to the macro enabled mode. It's almost impossible to just save it. It again is constantly being autorecovered. I've changed autosave to 30 minutes, because Excel shows as not responding, however in the Task manager, I can see it's probably doing an autosave, and CPU performance is around 50% for the process. I have noticed that the native file size is significantly smaller, but the time to load or save is significantly longer. I would trade time for disk space anyday. Any suggestions? I'm leary of converting any other work, and seriously considering returning to Excel 2003. Surely these types of things showed up prior to release. Is there a bug list or problem list that is available for the product? Any help would be appreciated. -- Ross |
All times are GMT +1. The time now is 07:02 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com