Anytime an application that previously worked stops working, or an
application that works on one machine won't work on another machine, the
first thing to check is the References collection. (All Access databases
contain references, which are a way of referring to another application's or
project's type library. In general, you want to ensure that the files
referenced in an Access application exist in exactly the same location on
the client workstations as they did on the development workstation, and that
each referenced file is the same version on all workstations.)
On the machine where it's not working, go into the VB Editor and 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, (the
selected references will be at the top of the list), 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 it/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)
Installing new software is a common cause of the References collection
getting messed up, as the new program may have changed the version or
location of a file the application's trying to use.
