My excel file is getting bigger and bigger and I’m pretty sure the code cleaner will to the work

Thanks
R

MORE OVER, many thanks for endless commitment to “giving back” So many people talk the talk but it is refreshing to see those who actually live it.

The excel community seems blessed with an abundance of benevolent giants who continually give back to all that follow behind them (like your, Stephen Bullen, Ron de Bruin, Dick Kusleika, Jon Peltier, Chip Pearson, Jan Karel Pieterse, Andy Pope, and SO MANY OTHERS. SO, very publicly, THANK YOU ALL FOR GIVING BACK SO MUCH.

@Everyone. Rob & Stephen have authored some GREAT books and AMAZON has a working PayPal button. It is certainly an easy way to give a little back in the other direction and, at the same time, gain so much more from your investment.

While this, take a look at:

http://orlando.mvps.org/VBADecompilerMore.asp?IdC=Word

Fnatstic utililty and is certainly on the check list of processes (along with smart indenter) to run perform before releasing any code.

I am curious to know how you handled the escape key being pressed. I have been trying to port a vba routine to vb6 (more for learning than anything else) and I’m have great differculty in letting the user stop the process. It may be because I’ve chosen to port a routine hat finds excel files on a drive using the recursive method.

I would like to second Roland’s comment on using versioning with subversion. This makes it easy. I now have several branches from the main development version. I was using clearcase for entire .xla file. This was almost no help in maintaining the source code between branches. With the new Code Cleaner I just export to the local checked out folder and then use TortoiseSVN to check it in to the remote svn server. I can pull a certain version to a local directory, import the directory to a fresh copy of Excel, add a few references I use then run the addin. Awesome!!!!

Because different people have spent a lot of time porting the Code Cleaner to Word in the past I tried to design it to make life easier for anyone who wants to port this version to other Office apps. I don’t need it enough outside of Excel to do it myself, but if you or anyone else wants to port it I’ll be more than happy to give credit and host it on my web site.

I wrote an add-in based on your code-cleaner tool to be able to use general source code versioning (other than VSS, which I dislike because several constraints imposed). The versioning tool currently implemented is Subversion and it’s cool windows client TortoiseSVN. The idea was to save the modules as source code files and put these under version control.

On the other side, you can then import back the source files into excel (at least class and standard modules).

There’s an additional goodie, you can simply compare Excel VBA code between files using a diff util like WinMerge.

A nice enhancement of this tool would be to generalize it to all VBA enabled applications using a COM add-in. I’ve seen that the codecleaner COM-Addin is still restricted to Excel, do you think it would be extremely hard to generalize it? At least to the Office applications?

Many thanks for this great tool, it’s (together with the VBA indenter) one of my favourites.

-regards,
Roland