[AccessD] Big Modules v. Small Modules

Hi Arthur

This is not what I recall to have read, which is that by calling any
function from a module the whole module is loaded.

On the other hand, no module is read into memory until one of its
functions is called. This should be one of the arguments for having
multiple modules. Another is that a function can be declared Private
within its module; that would be of no use, however, if a single mumbo
module is used. A third argument is that by having multiple
specialized modules you can easily reuse a module in another
application.

I - and I think most developers - do as you do.

/gustav


> I have heard and/or read that Access is smart enough to load only what
> it needs from any given module. This suggests that for multi-app
> reusable library code, you should just stuff it all into one huge
> module. OTOH, it will Access time to read said module and decide which
> components it needs in order to execute some specific chunk of code.
> (Once a module is loaded, it remains loaded and Access won't have to
> search again, as I understand the operations.)

> So, what is the prevailing experience and wisdom here? In my current
> project I have a dozen modules, each dedicated to a specific group of
> functionalities (for example, all the PDF support stuff resides in one,
> all the OutLook stuff in another, the API functions in another, etc.)
> Aside from the organizational benefits, am I gaining or losing anything
> with this approach?

> TIA,
> Arthur