A module is a container for one or more Sub and/or Function
procedures. It makes no sense to "call a module". Rather, you need to
call the procedure in the module.
Call ProcedureName
' or
Call ModuleName.ProcedureName
Note that a module can contain any number of Sub and/or Function
procedures. It is not required that a module contains only one
procedure (although it is harmless to do so).
Cordially,
Chip Pearson
Microsoft Most Valuable Professional
Excel Product Group, 1998 - 2009
Pearson Software Consulting, LLC
www.cpearson.com
(email on web site)
On Fri, 10 Apr 2009 10:42:08 -0700, Bishop
<(E-Mail Removed)> wrote:
>I have 2 modules in a particular Project. Each module is a Sub. I'm trying
>to call one module within another module and I'm getting the following error:
>
>Compile Error:
>Expected variable or procedure, not module
>
>The two modules are: TallySheetRepDump and BanSumSort
>
>This is how I'm trying to call the module:
>
>Sub TallySheetRepDump()
> Call BanSumSort
> ...
>
>I basically want the code inside BanSumSort to run immediately upon the
>execution of the TallySheetRepDump routine then continue with the code in
>TallySheetRepDump. What am I doing wrong?