It takes longer to call a sub to execute some code than it does to execute it
inline.
that said, it is not a significant performance problem and the benefits
probably outweigh the penalties.
The only limitation I am aware of is that if you exported a module to a bas
file, the size of the bas file should be less than 64K. This isn't a
published limitation, but many have stated it as a rule of thumb which if
ignored can cause problems.
That really has no effect on the number of procedures which I am not aware
of any limit.
At the same time, from a maintenance standpoint, I suppose you can go
overboard.

Signature
Regards,
Tom Ogilvy
> Greetings:
> I have a new module, consisting of many "subs"
[quoted text clipped - 6 lines]
>
> Thanks
Jim Thomlinson - 23 May 2006 22:01 GMT
To further what Tom has said, where you have a real need for speed
(performance is noticably poor) then keep function or procedure calls out of
large loops (a few thousand loops or more). There is overhead associated with
every call so if it is in a loop it can become significant. If it is just
regular sequential code then there really is no benefit to 'in lining" your
subs or functions, and maintenance will often be easier if you break your
code up into multiple subs or functions.

Signature
HTH...
Jim Thomlinson
> It takes longer to call a sub to execute some code than it does to execute it
> inline.
[quoted text clipped - 23 lines]
> >
> > Thanks
BEEJAY - 24 May 2006 12:42 GMT
Tom and Jim:
Thank You: Gives me quite some peace of mind
> To further what Tom has said, where you have a real need for speed
> (performance is noticably poor) then keep function or procedure calls out of
[quoted text clipped - 31 lines]
> > >
> > > Thanks