J
Joe Guerry
I have been succesfully importing dbase III files into an access database
for several years now. Recently I started getting "Unexpected Error fromm
external database driver (8458)". When I attempt to import or link to the
dbf.
I can not find any posts or kb articles with this specific error message. I
have attempted the fixes recommended for similar errors (re-register jet
dll's, etc), but no luck. I receive the dbf data from a third party who
export from FoxPro. I archive the dbf's, so I have tested this problem with
older data files that were previously imported, and get the same error. I
have tested this on three different computers, and the same error occurs on
each (all Office 2003 with all updates installed).
I have eliminated file name, file location, potential file damage and
registry errors through the above testing, and can not find the solution. I
do not have any borland products installed on any of the computers tested.
This problem first appeared at the end of September. I specutlate that
something was changed in one of the recent updates, and have considered
uninstalling the office updates as a test.
One last thing, when I try to import or link to the data, I am prompted to
select an index file. The data is not sent with an index file.
Thanks in advance for any help that can be offered,
Joe Guerry
for several years now. Recently I started getting "Unexpected Error fromm
external database driver (8458)". When I attempt to import or link to the
dbf.
I can not find any posts or kb articles with this specific error message. I
have attempted the fixes recommended for similar errors (re-register jet
dll's, etc), but no luck. I receive the dbf data from a third party who
export from FoxPro. I archive the dbf's, so I have tested this problem with
older data files that were previously imported, and get the same error. I
have tested this on three different computers, and the same error occurs on
each (all Office 2003 with all updates installed).
I have eliminated file name, file location, potential file damage and
registry errors through the above testing, and can not find the solution. I
do not have any borland products installed on any of the computers tested.
This problem first appeared at the end of September. I specutlate that
something was changed in one of the recent updates, and have considered
uninstalling the office updates as a test.
One last thing, when I try to import or link to the data, I am prompted to
select an index file. The data is not sent with an index file.
Thanks in advance for any help that can be offered,
Joe Guerry