L
Lee Buehler
We have a new XP computer that we have added to our NT network. There are
two other XP machines as well as 13 win98 machines on this network. This is
the newest machine and is the only one that has this problem. We installed
MS Office Small Bus Ed 2000 and then installed MS Access97 so that the
Access applications could be run from this machine. We renamed the
MSAccess.exe file that Small Bus Ed installed as that would conflict with
Access97. This is the same procedure that we go through on each new
computer and this is the first that has had a problem with it.
There is a macro that imports a txt file and then appends the data to tables
from which reports are generated and printed. On the new machine, we get
the error #3170 "Couldn't find installable ISAM". From the help files I
guess the location of the DLL that imports the data is supposed to be in the
registry but is not.
I have reinstalled access97, uninstalled and reinstalled with no
improvement. I suspect there is something in the registry or some place
that is corrupting the installation. I do not understand why this is a
problem on this machine and was not a problem on the other two.
Lee
two other XP machines as well as 13 win98 machines on this network. This is
the newest machine and is the only one that has this problem. We installed
MS Office Small Bus Ed 2000 and then installed MS Access97 so that the
Access applications could be run from this machine. We renamed the
MSAccess.exe file that Small Bus Ed installed as that would conflict with
Access97. This is the same procedure that we go through on each new
computer and this is the first that has had a problem with it.
There is a macro that imports a txt file and then appends the data to tables
from which reports are generated and printed. On the new machine, we get
the error #3170 "Couldn't find installable ISAM". From the help files I
guess the location of the DLL that imports the data is supposed to be in the
registry but is not.
I have reinstalled access97, uninstalled and reinstalled with no
improvement. I suspect there is something in the registry or some place
that is corrupting the installation. I do not understand why this is a
problem on this machine and was not a problem on the other two.
Lee