Hello,
I've had problems with Excel crashing in the past, but now I've finally been able to narrow it down a bit more and identify a repeatable procedure that will crash Excel.
My project is difficult to describe briefly, but basically it imports error log files from networked computers and does stuff with them -- the user can automatically create Pareto charts of error frequency or downtime, or search for a specific error, or graph hourly tool throughput compared to error trends, etc.
For the throughput section of my program, the files are quite big; one day might be 25+ MB worth of text. I copy the whole file into a new excel sheet, run my analysis, copy the results to a "Data" sheet, and then close the new worksheet. I then open a different set of files (to get the error logs), analyze that, graph those results, and then I include the throughput data from my "Data" sheet with those error series.
My program works fine for executing these operations, but I run into a problem when I try to save the sheets. I suspect that autosave triggers the same crash. Out of the 40+ tools that create these files, I'm currently interested in looking at 6 of them (4 are "WTS" tools, 2 are "ATS"). When I run the throughput analysis on multiple tools, and go to save my workbook, Excel crashes.
If I run the program on 1 tool and save, Excel usually does not crash. I can run 1 at a time, and save after each run, up until maybe 3-4 tools have been run; at that time the save triggers a crash again.
If I run the program on multiple tools but delete the sheets before saving, Excel does not crash. So I suspect that running my analysis corrupts the worksheets somehow.
I have run CodeCleaner numerous times (if I run CodeCleaner after analyzing the files instead of saving, it crashes Excel as well). I have ensured that all modules have "Option Explicit" on the top (actually, i haven't checked if my forms have that; I'll do that now). I've restarted my computer, but this bug is consistent. I checked the Error Report contents; "Code: 0xc0000005", which my co-worker told me was a pretty generic code that won't help me much. I'm using Excel 2007, and it's not in compatibility mode.
I noticed that running my analysis on the "ATS" tools is more likely to cause a crash. Those files are also typically larger than the WTS files.
I've attached my .xlsm file... I realize you won't be able to import the files and get the same problem I had, but maybe it will help.
Very grateful for any more ideas on what it could be, as people in my company will need to use my program, and it can't always be crashing like this.
Thanks much,
-Joe
Bookmarks