To do its job, Access (like most modern programs) makes use of various
external program and object libraries that provide functionality that may be
shared among applications. For example, Access always uses the Visual Basic
for Applications library, the version-appropriate Access Object Library, and
the OLE Automation library. References to the specific library files,
including their locations, are stored with your database. But these library
modules may not be in the same location on different machines, especially if
they have different versions of Microsoft Office. If you move a database
from one machine to another, these references may be "broken"; that is, one
or more of the library files may not be where the stored reference says it
is.
When this happens, you need to take steps to let Access repair the broken
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.
Here are Doug Steele's instructions for how to do it:
****Quote****
Open any code module (or open the Immediate 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).
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.
****Unquote****
So, follow those instructions and see if your problem goes away.
Check out the following reference
http://www.trigeminal.com/usenet/usenet026.asp?1036
Scott A wrote:
>
> I've been working with some Access 2002 reference
> materials, but am programming in 2000. There are a few
> things I have tried that involve using date parts, and
> every time I try them out I get an error. The latest one
> says Compile Error: sub or function not defined.
>
> I'm wondering whether there is support for date parts in
> 2000, or if I should be looking for something else.
>
> Any ideas?
Similar Threads
