GOGGS75
04-24-2013, 12:53 PM
Hi
I hoping someone can suggest any reasons for a problem I'm having or let me know if they have had the same problem.
A macro-driven spreadsheet I built has started crashing when saving it (cntrl-s). It comes up with an error message 'system error &h8000ffff' followed by an 'out of memory' message.
The spreadsheet has 7 userforms with quite a bit of code but I have built some larger than this before with no problem.
I have tried various approaches to sort this but the problem keeps coming back. The approaches have been as follows:
1.) Replace each worksheet (15 of them) with freash ones in-case something was corrupt.
2.) Make sure all objects are set to nothing at the end of the macro.
3.) Save some of the userforms as separate 'frm' files and load them when the macro runs.
4.) Convert the file to XML format then back to XLS to clear the macro completely, then rebuild it using frm files
5.) Try Ron Ron De Bruin's Code cleaner add-in
The same problem is occuring in Excel 2003 and when converted to an Excel 2007.xlsm file.
An error message at one stage was stating that the file could not be saved because somthing was wrong with a VBA or External component.
I am puzzled as to why the problem happens when saving the file and only sometimes happens.
Thanks for any advice.
Goggs75
I hoping someone can suggest any reasons for a problem I'm having or let me know if they have had the same problem.
A macro-driven spreadsheet I built has started crashing when saving it (cntrl-s). It comes up with an error message 'system error &h8000ffff' followed by an 'out of memory' message.
The spreadsheet has 7 userforms with quite a bit of code but I have built some larger than this before with no problem.
I have tried various approaches to sort this but the problem keeps coming back. The approaches have been as follows:
1.) Replace each worksheet (15 of them) with freash ones in-case something was corrupt.
2.) Make sure all objects are set to nothing at the end of the macro.
3.) Save some of the userforms as separate 'frm' files and load them when the macro runs.
4.) Convert the file to XML format then back to XLS to clear the macro completely, then rebuild it using frm files
5.) Try Ron Ron De Bruin's Code cleaner add-in
The same problem is occuring in Excel 2003 and when converted to an Excel 2007.xlsm file.
An error message at one stage was stating that the file could not be saved because somthing was wrong with a VBA or External component.
I am puzzled as to why the problem happens when saving the file and only sometimes happens.
Thanks for any advice.
Goggs75