 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Applications / Excel / March 2006Excel Crashes Killing Me
Excel 2004, SP 11.2.3 PowerBook G4, 2 GB RAM, OS X 10.3.9 I've been working on a complex Excel financial model for a month now. I was putting the final touches on the whole thing this afternoon when it suddenly crashed. Previous crashes (many) left the model in a stable state and recoverable. The model has about 400 names ranges and many macros. It generally has been running stably. Unfortunately, that's not the case tonight. I save sequential backups frequently by shutting down Excel, duplicating the file in the Finder and naming the backup file with a numerical sequence number. I've got 70 previous versions. The latest version crashes Excel very soon after opening the file. Troubleshooting includes: 1. Running DiskWarrior and TechTool Pro 4 2. Running Disk Utility to repair permissions 3. Reinstalling Excel 4. Reinstalling the latest SP 5. Trashing all the prefs files 6. Turning off all but a few fonts in FontBook 7. Reverting to a previous version of file (went back about 3 versions). This will require re-creating the already completed work from the last day or two. It seems all for naught, however. It looked promising for a while, but the crashes keep coming back, even with a previous version of the file. Crashes occur shortly after opening the file. I don't know if Excel is stable with other worksheets. I am so sick of the crappy performance and reliability of Excel on my Mac that I'm very seriously tempted to run out and buy a PC tomorrow. I never had these problems on my work PCs. This is a major consulting project that is overdue and I've got to get it done pronto. I'm losing hours and hours of productivity on these problems (at least 8 hours this afternoon and evening so far). Ideas? Steve <snip description of problem> > I am so sick of the crappy performance and reliability of Excel on my Mac > that I'm very seriously tempted to run out and buy a PC tomorrow. I never > had these problems on my work PCs. As an aside, I would like to point out that the ONLY times I've ever had Excel crashes is on PCs, both work and home. Don't rush off yet! > This is a major consulting project that is overdue and I've got to get it > done pronto. I'm losing hours and hours of productivity on these problems > (at least 8 hours this afternoon and evening so far). Problems only ever seem to manifest themselves when under pressure, don't they?! > Ideas? The best idea I can think of at the moment (bearing in mind the time pressure) is to open a brand new spreadsheet. Copy all bar one row or column from the problem one onto the new one (repeat for all work sheets). Check that this works OK. Then copy in macros a few at a time and check again. Hopefully you'll end up with a "clean" version that is missing all the dross that causes crashes. If the crash manifests itself as "freezing", rather than shutting down, then the second best idea is that it isn't actually crashing, but is still processing. Perhaps give it a little longer to catch up. Unfortunately, however fast software works it is never actually instantaneous. PhilD -- <>< Thanks, Phil. That is exactly what I did about halfway into the project when a similar problem occurred. At that point, the VBA macros became corrupted and refused to recognize the last "End Sub" or "End Function" in a module. It took me a whole day to reconstruct the thing (something like 15 sheets, 500 range names, lots of graphs). I think as a last ditch I'll try to open it on a PC at Kinkos. Maybe that will work. Steve For ref., McGimpsey talks about the problem I had last time at http://www.mcgimpsey.com/macoffice/excel/04/xl04bugs.html#deletedcode Deleted or renamed procedures corrupt modules I haven't been able to track this down entirely, but whenever procedures are deleted or renamed, there is a chance that remaining macros will fail with a "Compile Error: Only comments allowed after End Sub..." Workaround: Copy the remaining macro(s) (only ) in to a new module, delete the old one, then close and reopen the workbook in article 1143199137.956406.204490@i39g2000cwa.googlegroups.com, PhilD at phildeaves@yahoo.co.uk wrote on 3/24/06 3:18 AM: > <snip description of problem> > [quoted text clipped - 31 lines] > -- > <>< Phil...seems to be a Mac-related problem. I took my corrupt files to Kinkos and they opened just fine on a Dell PC running Excel 2003 under Windows 2000. I continued my development for almost 3 hours without a single crash. I'm getting some flaky behavior in Excel and in Entourage, so I think I will completely remove and reinstall the MS Office 2004 suite. I wish MS apps were as stable on Mac as they are on PCs. The underlying OS X is pretty stable, but the MS apps are not very great. That creates a conundrum -- should I go buy a PC laptop now to get stable Excel. Or wait until Vista is released? Or just tolerate this abominable situation on my Mac? Poor MS QC makes me really angry. Steve > <snip description of problem> > [quoted text clipped - 31 lines] > -- > <>< > Excel 2004, SP 11.2.3 > PowerBook G4, 2 GB RAM, OS X 10.3.9 [snip] Hmm, I've been getting crashes since the latest Office update, but only on the computer running 10.3.9. On my other computer (10.4.5) I haven't had Excel crash yet (granted, I spend more time working in Excel on the former computer). Still, I wonder if the latest update is not playing well with Panther? _d |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.