cthend said:
I am starting to get VBA compile errors when ever a control is
clicked and I don't get it with Win2kpro boxes.
This has nothing to do with MDAC. Any Access file can contain broken COM
references that only occur on some computers and not on others. This is
usually caused by the developer adding extra references beyond the default
ones. A practice that is not recommended for files that need to run on more
than one PC.
In some cases the additional references are accidentally added or get added
when experimenting with objects that ultimately end up not being used.
Those references are not actually needed so deleting them is a quick and
easy fix.
You need to open the VBA editor window on the PC having the problems and
then go to Tools - References. The references that are set for the file
will all be at the top of the list and will be "checked". Look for the word
"MISSING" following any of those checked references. Those will be your
problem.
You can also create a brand new empty file and examine the references in
that file. Those checked references will be the default ones. If your
problem file has any references beyond the defaults and those are the ones
that marked "MISSING" then you need to determine if those references are
really required.
You can un-check them one at a time and then attempt to compile the project
(on the PC that works). If it compiles without errors then you don't need
that reference. If you get compile errors that go away when the reference
is restored then you either need to eliminate that dependency in your app or
you need to install and register that referenced library on the other PC
(assuming you have a legal right to do so).
