Windows XP base component requirements for Access 97

[Mark@PCICS]

Installed Office 97 Pro with service packs on a newly installed WXP Pro
system 3rd quarter 2005. Installed Access 97 application at that time and it
operated successfully until late 4th quarter 2005. I'm curious about the
versions of the core support requirements (MDAC, JET, DAO, etc) that WXP and
Off97 require in order to operate successfully, because....

A function within the Access 97 application has begun to fail. The function
involves displaying (rather, failure to display) information on a form for a
newly selected data object from a list of data objects. Some objects display
their data in the form successfully. ALL other computers accessing this
database (W98 and WXP using Off97) operate successfully. I've uninstalled and
reinstalled all Office and application components on this computer with no
change in symptoms.

So, I wonder whether a support (base) component on the system in question
has changed, become corrupted or even upgraded around the time of initial
failure. I see no signs, and have no indication from the client, that there
were any client-induced changes.

 

[Douglas J. Steele]

I suspect it has nothing to do specifically with the combination of Access
97/Windows XP, but simply the fact that your References collection has got
messed up.

References problems 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://www.accessmvp.com/djsteele/AccessReferenceErrors.html, or check my
December, 2003 "Access Answers" column in Pinnacle Publication's "Smart
Access" (you can download the column, and sample database, for free at
http://www.accessmvp.com/DJSteele/SmartAccess.html)