Hi Hans,
>
>I had already searched the DL section, but did not find anything. This might have been my failure.

Download #26287 - I was not sure of my memory so I searched now. From a quick glance at the source: identifies small problem areas in comments, so probably usable, big drawback IMHO seems to be that it doesn't build a calling chain (where possible <g>) of functions/procedures encountered.
>
>So I went to foxmasters.com, downloaded the +CodeInspector and tested it on a lengthy procedure file (> 5000 lines of code) and a smaller project: Bingo! It did what I was looking for. I will stop searching now and will start using this tool! The 40 EUR, which it costs, are well spent.

That I don't doubt - 40$ is less then searching and testing other tools, UNLESS the other tool saves even more work<g>.

>Well, the way may have been long, but finally rewarding - so again many thanks for you answer!

Do you get the source to tweak yourself ? Can you define some global vars which won't get flagged like goApp in an external file, so it won't clutter your sources in every third method ?

And most of all, does the tool *try* to build a calling sequence from the code to get a better picture of privates already in use ? Should be the most demanding part, but as the calling hierarchy could be displayed back in FP days, not insurmountable <g>.

regards

thomas