Has anyone got a method for scanning VBA code and reporting references to
custom Subs, Functions, Classes, and Forms?

I want to package some of my macro library for distribution, but I don't
want to include subprograms that aren't actually required by the exported
subset.

hi,
see this site.
http://cpearson.com/excel/vbe.htm
Regards
FSt1

"Allen_N" wrote:

> Has anyone got a method for scanning VBA code and reporting references to
> custom Subs, Functions, Classes, and Forms?
>
> I want to package some of my macro library for distribution, but I don't
> want to include subprograms that aren't actually required by the exported
> subset.
>
>

That site has some very useful code (thanks for the link!), but it doesn't
say how to do what I want.

I'm looking for a routine that will identify all calls to Subs, Functions,
Forms, and user-defined classes. In other words, what a compiler does in one
of its passes through the source code. This would allow a developer to ensure
that an Add-In actually contains all the Subs etc. that the macros require
beforehand, rather than relying on trial & error after releasing the Add-In
to end-users.

"FSt1" wrote:

> hi,
> see this site.
> http://cpearson.com/excel/vbe.htm
> Regards
> FSt1
>
> "Allen_N" wrote:
>
> > Has anyone got a method for scanning VBA code and reporting references to
> > custom Subs, Functions, Classes, and Forms?
> >
> > I want to package some of my macro library for distribution, but I don't
> > want to include subprograms that aren't actually required by the exported
> > subset.
> >
> >

MZ-Tools addin ?
http://www.mztools.com/index.htm

NickHK

"Allen_N" <(E-Mail Removed)> wrote in message
news:B0C3ECA5-01BF-48D1-9958-(E-Mail Removed)...
> That site has some very useful code (thanks for the link!), but it doesn't
> say how to do what I want.
>
> I'm looking for a routine that will identify all calls to Subs, Functions,
> Forms, and user-defined classes. In other words, what a compiler does in
one
> of its passes through the source code. This would allow a developer to
ensure
> that an Add-In actually contains all the Subs etc. that the macros require
> beforehand, rather than relying on trial & error after releasing the
Add-In
> to end-users.
>
> "FSt1" wrote:
>
> > hi,
> > see this site.
> > http://cpearson.com/excel/vbe.htm
> > Regards
> > FSt1
> >
> > "Allen_N" wrote:
> >
> > > Has anyone got a method for scanning VBA code and reporting references
to
> > > custom Subs, Functions, Classes, and Forms?
> > >
> > > I want to package some of my macro library for distribution, but I
don't
> > > want to include subprograms that aren't actually required by the
exported
> > > subset.
> > >
> > >