Compile Error in hidden module (help)

[Michael F via AccessMonster.com]

Does anyone know what Compile Error in hidden module: Form_NCMR_DB_FRM_Load,
means. The NCMR is the name of the database, but I have never had that come
up before. If anyone could help I would greatly appreciate it.

 

[John Spencer (MVP)]

Are you trying to make an .mde file? Or are you doing something else? In other
words, when do you get the error?

If it is when you are trying to make an mde, this error means that there is a
problem with your VBA code. Open any module and select Debug.Compile. The
compiler will attempt to compile the vba code and should stop on a line and
indicate an error. Identify the error, fix it, Save your code, try to compile.
Repeat until all errors are fixed.

Now try to make an .mde file.

 

[Michael F via AccessMonster.com]

The error occur right after it loads her permissions for the database, the
database is trying to open and the error, "Compile Error in hidden module:
Form_NCMR_DB_FRM_Load" appears, not real familiar with access, she is just
trying to access the database is what she is trying to do. She has all the
permissions and correct workgroup. Does anyone have any suggestions, she is
using Access 97.

 

[John Spencer (MVP)]

I have no idea what is causing the problem. Although I would check for missing
references if this is working on one computer and not another.

Try launching the application while holding down the shift key. That may put
you into the design mode. Then look for the form and check the code in the load
event to see if it could be generating an error. Also check and make sure the
user has no missing library references.

Here are MVP Doug Steele's instructions for how to repair the broken
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.

This 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)

For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains the
specific function that's failing doesn't have a problem.

**** End Quote ****