Reducing File Size

I'd be interested in any comments about Ribbon Commander VBA cleaner vs Rob Bovey's CodeCleaner. Is one better than the other?

Dear
my excel file size is 25.4 MB (26,697,811 bytes) i can't open please kindly suggest me how to open my excel file

The easiest way to remove all VBA code from a macro-enabled Office file is to save the file in a macro-free format. For example, save a .xlsb workbook as .xlsx

However you should not open any workbook that you suspect that it has malicious macros or code with bugs that may damage your data or PC. If you disable macros, then you are left with no choice other than to delete macros manually or open and save each file in a macro-free format.

However, the Macro Mover add-in allows you to mitigate security risks and work more productively:

Macros are removed from closed files only! There is no need to disable all macros from the Trust center. Your files will not be opened in Excel, so VBA code cannot be executed.

Code is deleted from closed files, so you don't have to wait while opening/saving large files.

VBA code can be removed from any macro-enabled Office file (including add-ins), even from locked VBA projects.

Macros can be removed without changing the extension of the file. You can still take advantage of the high compression ratio offered by binary files (.xlsb), while erasing macros fast

Read more:

http://www.spreadsheet1.com/move-excel-vba-projects-from-one-workbook-to-another.html

Ribbon Commander offers the CleanVBAProject method, which can remove all code garbage from any macro-enabled or binary workbook and Add-ins instantly.

The Ribbon Commander VBA cleaner removes all redundant caches from closed files, so VBE doesn't get a chance to replace the information.

Cleaned files are smaller in size. Nowadays files are moved between desktops and the cloud more frequently than ever before. On an enterprise level, smaller files translate into decreased costs for online storage and bandwidth. Backups and downloads can be executed faster. Email bouncebacks could be stopped and email storage requirements could be reduced.

For years the 'golden' standard for Excel VBA code cleaning has been module export - import.
Ribbon Commander aims to raise the bar by offering several productivity advantages for VBA developers.

Reclaim existing storage space on desktop PCs and servers by replacing large macro-enabled Microsoft Office files with smaller versions. Slow storage growth as new files are added.

Read more:

http://www.spreadsheet1.com/vba-project-code-cleaner-for-access-excel-powerpoint-word.html

Thank you David Baker - previously I would try manually selecting the column beyond my last entry, Shift+Ctrl+Right-arrow to select all rows to right and then right-click delete; and then similarly for rows.

Of course nothing bloats a workbook more that setting it up as a shared workbook that can be opened and edited by different users at the same time. Even if one limits the number of days that the change history is kept for, the file size seems inevitably to expand. The solution I use is somewhat clumsy, but I work out the file size when empty of data (but with headers, formating, any lookup tables for validation rules, macro code etc) and then how it increases with additional rows of data. This allows a macro to then calculate what the approximate size of the file should be for the given number of rows of records it has. A macro then automatically:
a) checks if the actual file size exceeds a preset multiple of the calculated presumed size (e.g. x3)
b) checks if the number of active users is just 1
c) then will offer to unshared the workbook (which causes the file to be saved), and then resaved again as a shared workbook.
This inelegantly but effectively clears the history and the bloating for shared files.

Hi Allen

Thank you for your useful Excel and Word tips - great work.

Excel file bloat is problem that I have seen a number of times over the years even in workbooks without macros. There is an excellent piece of code that I have used successfully over the years, ExcelDiet.

http://www.vbaexpress.com/kb/getarticle.php?kb_id=83

The results have been outstanding in some situations when Excel gets confused about the actual range used by the workbook.

Cheers David