Your question prompted me to look again for a tool like this. I found one
that looks promising.
http://www.aivosto.com/project/project.html

> -----Original Message-----

> Jim Phillips <[log in to unmask]> wrote in message
> news:<[log in to unmask]>...
> > We have a rather large Visual Basic project with only a few
> forms but with
> > lots of functions and procedures.  I'm looking for some
> kind of tool that
> > will show me where the various functions and procedures are
> called from, so,
> > for instance, if we need to change the "GenerateFile"
> procedure, we can see
> > where in the code it is called from.  Any ideas on tools that create
> > documentation?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *