Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Check for unnecessary Public variable declarations and duplicate Set statements
I already use Rob Bovey's excellent code cleaner [
http://www.appspro.com/Utilities/CodeCleaner.htm ] but I was wondering whether something exists that checks for duplicate Set statements and unnecessarily declared variables in a project? I have a project that has evolved over a couple of weeks, and I've refined it to be a lot smaller than it once was. The code is spread across 12 modules and I declare all the variables as Public in a module on their own. The variables are mostly Workbooks, Worksheets and Ranges, but there are also Integers and Longs, and there are a lot of them (100+). I know that some of the variables aren't actually used in any of the modules, after the refining that I've done to the project over the weeks. The code is made up of one or two Sub procedures per module - some very long - with a master Sub calling the other Subs in sequence. During testing of the separate procedures I've had to copy in a lot of the Set statements (to define Workbook, Worksheet and Range variables) at various points in each procedure, so that I can test each Sub in isolation. But now that the Project is finished I've put all these Set statements at the beginning of the master Sub, which means that they're not now needed in the individual Subs. Short of using the Find tool in the VBE to look for unused variables and duplicate Set statements, is there a quick of doing this? TIA Ian |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Public Variable | Excel Programming | |||
Public variable | Excel Programming | |||
Declarations Procedure and Duplicate Declarations | Excel Programming | |||
Check to see if variable is duplicate. | Excel Programming | |||
Strange variable declarations | Excel Programming |