Access problems after new computer install

[Joseph Moran]

Hello all.

I'm hoping someone can help me with an Access 2000 problem.

I recently replaced a client's haggard, 6-year old Windows
98 system with a brand new Windows XP machine. One of the
applications that was being used on the old machine was
Access 2000, and the database being accessed was located
on the company server, not the local machine.

I assumed (incorrectly, evidently) that since the database
was on the server, that there would not be any problems
accessing it from another machine, especially if it was
with the same version of Access.

Therefore, when I set up the new computer and re-installed
Access 2000, I exactly re-created the desktop shortcut to
the existing database, and it launched, so I figured all
was well with the world.

However, the individual using the machine soon informed me
that the database was no longer working correctly.

Without going into too much detail on the specific
problems (there are several), it seems that from the new
machine, the database doesn't display or print properly,
and when reports are run, there are errors shown.

If you access the database using the old machine though,
everything is AOK. I can infer from this situation that
the database configuration is not self-contained within
the actual file, and that there is something customized in
the application configuration that has changed.

The original database and Access 2000 installation was
done by someone that is long gone, and I don't know much
about Access. Thus, I've been unable to determine what
settings might be different on the new machine, or how to
import application settings from the old copy of Access
2000 to the new one.

KB has been no help, so I'm hoping someone can suggest
something or point me in the direction of a solution.

Any information will be greatly appreciated. Many thanks.

Regards,

Joe

 

[Douglas J. Steele]

Your references could be messed up.

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://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

 

[Joseph Moran]

Doug,

I'll give it a try. Many thanks for the detailed answer.

Regards,

Joe