Likely a problem with the References collection. This is common if there areReference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11076
different versions of software between the machine where the application was
developed and those on which it's going to be run.
On the machine(s) where it's not working, open any code module, then select
Tools | References from the menu bar. Examine all of the selected
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, under the Debug menu), 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)
Doug Steele, Microsoft Access MVP http://I.Am/DougSteele
(no e-mails, please!)
"Ron" wrote in message
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11076
> HELP ... everything I read says that an Access 2000 db should run with no
> problems under 2003. However, this is not my case. The db under 2000 has
> for years and now with 2003 I get errors that seem to be related to
> "built-in" functions that 2003 says it can't find.
> I have tried this db under Office XP and it functiions without problems.
> I do NOT have data Access Pages which is the only thing I find as needing
> I need to transfer this project to a person that has 2003 and we need it
> running soon.
> Thanks for any and all help anyone can provide.