Re: too many modules

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks Marshall,

Hard to imagine and true, we have enough forms and reports with code behind
them that we are worried about module count. We only have 32 pure modules,
the rest are behind forms and reports. I will look into the library database
concept and see what it does for us. Thanks for the help.

"Marshall Barton" wrote:

jWhytis wrote:
I have an MSAccess database that is slowly creeping toward the maximum
allowed module count. I have been asked to find a workaround past this
limit. We are currently using Access 2003 and are planning to migrate to
Access 2007. Before the databases are distributed to the users they are
converted to mde files.

I have created a solution that launches a “parent” access .mdb/mde and
spawns “child” mdb/mdes using automation. The idea here would be to spread
the forms & modules across multiple mdbs and switch between them based on
user need. This works with the notable problem of when the child apps need
to act on the parent app the only way to reference the “parent” is to use the
getObject method. While it works in test, the parent app has to be the first
MSAccess application open and the doc on getObject says the order of objects
returned is not guaranteed.

Because of these problems I’m being asked if there is a way to:
1. Create two mdes, Amdb.mde and Bmdb.mde and from Amdb.mde call a form in
Bmdb.mde in such a way the form from Bmdb.mde comes up in Amdb.mde.
2. Use references to create forms/modules that reside outside the mde file
but can be used within the mde – Perhaps ActiveX controls or dlls?
3. Some other thing we have not been clever enough to think of.


It's is very difficult to imagine a db with a thousand
form/report modules, class modules and standard modules.

How about just combining bunches of your standard modules?

A relatively sane approach is to create a library mde with
many/most of your existing standard modules.

Using forms/reports in one db from another db is not
something to get involved with if there is any other way to
deal with the problem.

--
Marsh
MVP [MS Access]

.

Relevant Pages

  • Re: Authors liability question
    ... Imagine a different story in which a real media figure -- Wolf ... presented as fiction is pretty much in the clear. ... the story Tokyo is flattened and in the story Wolf reports it, ...
    (misc.writing)
  • Re: Ghost caught pinching bums
    ... A MEDIUM has been called in to investigate reports of a ghost that was ... CXan you imagine the poor bugger who happens to ... be standing or walking behind some female who ...
    (soc.men)
  • Re: too many modules
    ... Another thing to consider is that many of your forms and reports might have ... Option Compare Database ... the parent app has to be the ... Use references to create forms/modules that reside outside the mde ...
    (microsoft.public.access.modulesdaovba)
  • Re: OT: Bad Research, Worse Reporting on Global Warming
    ... scientists polled felt pressured to change their reports." ... imagine a 0.7 percent kook rate, ... personally experiencing pressure to change ... We'll ignore the ambiguous nature and questionable significance of ...
    (sci.electronics.design)
  • Re: Access Size Problem
    ... ONLY works well for code that you have in standard modules. ... and put similar parts of the application (forms + or reports) into ... So, for example, the code to prompt ... forms need to be built in theses cases (your report prompt screens will use ...
    (microsoft.public.access.formscoding)