I'm looking for a beta-tester to communicate by email about my recent addition to my Procedure Stripper.

The original Procedure Stripper identified Word97/VBA procedures that were no longer in use within a template - deadwood, so to speak.

I have added another module which examines all data identifier declarations (Public, Private, Const, Dim, Static) and produces a list in the log file of all identifiers that IT THINKS could be deleted with impunity.

If you habitually define data identifiers (Dim etc) near the head of a procedure, write executable code in the body, and then delete that code and forget (or like me are too lazy) to delete the definitions, the results of this new macro may astound you.

Before I get the GUI form all dressed up I could use some feedback on how well it is doing, and what user options might be called for.

If you want to d/l the locked template you can do so at <A target="_blank" HREF=http://www.vif.com/users/cgreaves/ProcedureStripper.htm>Procedure Stripper</A>.

Open and unlock one of your Word97/VBA templates as the ActiveDocument and then run the command "ProcStrip.IdentifiersData.TESTGetDataIdentife rs" from the Procs toolbar menu. On Word's status bar you'll see a little counter running through all the data identifiers it has located, and at the end of the run you'll find a file Procs.TXT in your template directory listing all the suspect identifiers. The onus is on you to remove that file before the next run; I write to the log file in Append mode.

I am indebted to Payne Consulting for ideas about analysing lines of VBA code. Please visit their site at <A target="_blank" HREF=http://www.payneconsulting.com/>http://www.payneconsulting.com/</A>.