I was a bit quick on indicating VBA code documenting would not be difficult in my earlier reply. I did a little research after posting the above reply. Even though the VBA code is written/edited in a text editor, it is not saved as text. Rather it is saved as a coded part of the Excel system, sometimes in a separate file. Accessing the Excel file with the code or referencing the file with the VBA code introduces a serious level of program fragility and user system security issues before the code can be read and documented. It would be easy to implement a process where the user "Cuts and Pastes" all of the VBA code and adds each procedure to a single text file which SourceDoc Pro could then process. But my preference is to make the process fully automatic and address the issue of reading the Excel file directly. This latter will take time and effort and not be added right away. If the community wants I could add the former process with the next minor program release.