Access 2000 trouble with dBaseIV ODBC

[tman138]

I have an Access 2000 database that was created with WIN98Se and contains a link to a dBaseIV table. This database runs fine in WIN98. My problem is that I have recently deployed a WIN2K Advanced Server running terminal server for remote users to connect. I cannot get any machine running WIN2K or WINXP to connect to the dBaseIV linked table. I get an 'Unexpected error from external database driver (8458)' error. I researched this error and could only find Q306095 in the Microsoft knowledge base. It recommends shutting down the Borland database engine to solve the problem, or installing the latest version of MDAC from Microsoft. Neither of these solutions was of any help since the problem occurs even if I copy the tables from the dBase server locally first, and I am running WIN2K SP3 which contains the latest MDAC components. I think my problem is with a buggy odbcjt32.dll This problem is easily demonstrated by opening an empty Access 2000 database in either WIN2K, WIN2K Advance Server, or WINXP and trying to either import or link to a dBaseIV table. I sent my $99 service call request to Bill G. but haven't heard anything yet.
Anyone got any ideas??

 

[tman138]

Allow me to reply to my own posting. My original post was somewhat misleading because it involved the dBaseIV Jet ISAM and not ODBC but it turns out that the problem is due to a missing registry key that controls whether or no Access loads the Borland Database Engine. The fix can be found at

http://support.microsoft.com/default.aspx?scid=kb;en-us;248841