Acces 2000: Module not found

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

JJoe - 09 Apr 2005 17:20 GMT

This is a followup to my message dated April6, 2005.
A recomendation was made by Scott McDaniel to Compile. Thanks toScott for
this recomendation.

As a followup note, I would like to add that this particlular error message
happens only on one workgroup PC. This workgroup PC is connected to to the
workgroup server thorugh a repeater > switch > router > server.

However, this very same workstation can access and read two other MDB files
on the same server fine at all times.

The funny thing is this workgroup PC generates the message below only when
accessing one MDB file and it is only this workgroups PC on the workgroup
network from all te other five that experiences this problem.

I have looked at CPU performance on this PC - it is constantly at 100 -
svchost and system are the two processes that have CPU utilization of 67 and
33 respectively.

A network trace reveals a whole lot of SMB traffic

Any suggestions would be apreciated

I have a situation that I have spent hours trying to figure out with no
success and would appreciate if someone could help me out.

Basically the setup is like this:

A Windows2000 workgroup server hosts three mdb files that can be accessed
from 7 workgroup computers on this workgroup network.

All 7 computers can access two of the mdb files on the workgroup server;
however only six can access all 3 mdb files. One workgroup computer receives
an error message when it attempts to open the file which is cleary visible.

_____________________________________________
"The expression On Open you entered as the event property setting produced
the following error: Module not found.
* The expression may not result in the name of a macro, the name of a
user-defined funtion or [Event Procedure]
* There may have been an error evaluating the function, event, or macro.
OK
_____________________________________________

Does anyone knw of a solution or a hint?

Reply to this Message

Douglas J. Steele - 09 Apr 2005 20:01 GMT

Anytime an application works on most, but not all, computers, or suddenly
stops working on a computer, the first thing to check is where there's a
problem with the References collection.

References problems can be caused by differences in either the location or
file version of certain files between the machine where the application was
developed, and where it's being run (or the file missing completely from the
target machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> This is a followup to my message dated April6, 2005.
> A recomendation was made by Scott McDaniel to Compile. Thanks toScott for
[quoted text clipped - 43 lines]
>
> Does anyone knw of a solution or a hint?

Reply to this Message

JJoe - 10 Apr 2005 05:40 GMT

Thank you very much Mr. Steele for your detqiled response to my request. I
will try this out on Monday and feedback to the group. Thank you once again.

Joe

> Anytime an application works on most, but not all, computers, or suddenly
> stops working on a computer, the first thing to check is where there's a
[quoted text clipped - 72 lines]
>>
>> Does anyone knw of a solution or a hint?

Reply to this Message