Hi,
I have an application in development that currently has about 50 heavily interconnected sheets (including graphs), several dozens of VB functions and is more than 4 MB size, from which the actual data takes only the small part. And apparently it's not the end. While I've been considering the possibility of splitting the file to several smaller sub-tasks, I wanted to know whether I gain much from it. So I removed about the half of sheets and graphs that the remaining part could work without (the vice versa would be harder, but that's a problem I'll not bore you with) and saved the resulting workbook in a separate file. It was somewhat bigger than I expected. Intrigued, I removed *all* existing sheets (and inserted a new empty one so that Excel would have something to work with), all procedures from VB project, and all references to named ranges, styles and custom menus that the workbook ever had (I think that's all that can be manually removed). The resulting file was still more than 640 KB - while a new empty workbook is only 15. I opened the file in the Notebook... not that I could understand a lot, of course, except that about 2/3 of the file consists of similarly looking 128-byte info blocks. What's more interesting was that in the remaining part of "junk" I discovered names of various controls, VB procedures and variables, including those that were removed from the project long ago during development. I suppose that if I looked inside contents of separate worksheets (and had means to separate the sheep from the goats) I'd see some obsolete junk there as well.
So the question is: is it possible to "compact" an Excel workbook and is it worth the effort? The size per se doesn't bother me *too* much, but the performance of the app sometimes seems to suffer.
Thanks.
I have an application in development that currently has about 50 heavily interconnected sheets (including graphs), several dozens of VB functions and is more than 4 MB size, from which the actual data takes only the small part. And apparently it's not the end. While I've been considering the possibility of splitting the file to several smaller sub-tasks, I wanted to know whether I gain much from it. So I removed about the half of sheets and graphs that the remaining part could work without (the vice versa would be harder, but that's a problem I'll not bore you with) and saved the resulting workbook in a separate file. It was somewhat bigger than I expected. Intrigued, I removed *all* existing sheets (and inserted a new empty one so that Excel would have something to work with), all procedures from VB project, and all references to named ranges, styles and custom menus that the workbook ever had (I think that's all that can be manually removed). The resulting file was still more than 640 KB - while a new empty workbook is only 15. I opened the file in the Notebook... not that I could understand a lot, of course, except that about 2/3 of the file consists of similarly looking 128-byte info blocks. What's more interesting was that in the remaining part of "junk" I discovered names of various controls, VB procedures and variables, including those that were removed from the project long ago during development. I suppose that if I looked inside contents of separate worksheets (and had means to separate the sheep from the goats) I'd see some obsolete junk there as well.
So the question is: is it possible to "compact" an Excel workbook and is it worth the effort? The size per se doesn't bother me *too* much, but the performance of the app sometimes seems to suffer.
Thanks.