Controlling Module Loading

  • Thread starter Thread starter JonWayn
  • Start date Start date
J

JonWayn

Do I have any control over what, or the number of modules that open when I
open an Access 2003 database? Whenever I open a database that I have, which
references a 6MB library mba, or when I open the library itself and a module
it contains, there is quite a delay before I can do anything with the opened
database. How do I control this behaviour?
 
On Mon, 18 Feb 2008 19:20:00 -0800, JonWayn

You may have to live with this, and focus performance improvements in
other areas.
6MB on a 100 mbits/s network, you do the math.

-Tom.
 
No, but good effort. That's 100 M*bits*, not bytes, and you divided the
wrong way around. :)

So take 6MB, multiply by 8 and let's add 10% for network overhead (probably
a lot, but we're ball-parking). I'm not sure if 100 Mb is true-1024-M or
1000-M, but taking worst case scenario, we've got (1.1 * 6 * 1024 * 1024 *
8) / 100,000,000 ~= 0.55 seconds.


Rob
 
So, I'm human. I probably won't notice the difference between .55 seconds
and .01667 seconds. Either way, I don't think we have a reason for the
poster's perceived delay.

--
John Spencer
Access MVP 2002-2005, 2007-2008
Center for Health Program Development and Management
University of Maryland Baltimore County
..
 
There isnt even any network involved here. I was doing work on both
databases; going back and forth between the two to fix library bugs during a
debugging session. During that session, each time I opened the library and
any one of its module, I'd get a 10 seconds delay. The same would happen when
I opened the client database. However, after closing that session, new day,
rebooting the computer, the problem seems to have vanished. Dont know why
they acted so slowly the night before. Thanks for the feedback guys
 
Forgive me for not being a computer math wiz, but, what are the 8 and the 2nd
1024 in the equation for? With my limited math knowledge, it would seem to me
that : given 100 m-bits/s, what needed to be done was convert 6MBs to m-bits
(multiply by 1024 or 1000 whatever). Then by 1.1 for the 10% network overhead
allowance. Then, divinde by 100 (conversion). Where am I going wrong here?
I am sure I am being overly simplistic somewhere
 
The 1024's are to convert megabytes to kilobytes to bytes, and then the 8 is
to convert bytes to bits. As to your approach, you're on-target. I just
used the lowest common denominator of converting everything to bits, but you
could convert to Mbits if you wanted to.


Rob
 
BTW, if you assume that the 6MB and the 100Mbits are using the same
definition of Mega instead of 1024 vs. 1000, then it becomes MUCH simpler:

6 * 8 (to convert to Mbits) * 1.1 for 10% overhead = 52.8
then 48 Mbits / 100 Mbits/sec = 0.528 sec.



Rob
 
There isnt even any network involved here. I was doing work on
both databases; going back and forth between the two to fix
library bugs during a debugging session. During that session, each
time I opened the library and any one of its module, I'd get a 10
seconds delay. The same would happen when I opened the client
database. However, after closing that session, new day, rebooting
the computer, the problem seems to have vanished. Dont know why
they acted so slowly the night before.
Click to expand...

Where you manually compiling both before trying to open the app? If
not, then the 10 seconds was surely the compilation delay. If you
manually compile or distribute an MDE, there won't be any delay at
all due to compiling.

You should turn off COMPILE ON DEMAND, though. It compiles too much
and causes crud to accumulate that can lead to code corruption.
 
Back
Top