• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 311
  • Last Modified:

Access cannot link to dbf files

I am trying to help a user who has an application written in dBase IV.  They use Office 2000.  Access sits on the users desktop and the dBase tables are on their server.  I am simply trying to link to the dbf files on the server.  When I try to link. the "Files of type" only shows mdb and ODBC databases.  There is no option in the drop down for dBase files.  If I put "*.*" in the file name I can see the dBase files.  When I attempt the link I receive an error message that says "Unrecognized database format".  I am quite sure this is because there is no option to select dBase IV and therfore Access thinks it is trying to link to an mdb and obviously it is not.

Other systems I have worked on, this option was always there so I am lost as to what to do.  I have created an ODBC connection using the driver do Microsoft database.

Any and all help would be greatly appreciated!
0
jschmidt123
Asked:
jschmidt123
  • 5
  • 4
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Other systems I have worked on, this option was always there so I am lost as to what to do.  I have created an ODBC connection using the driver do Microsoft database.>>
  unfortunately, because of a lost law suit by Microsoft, your only option is to export from dBase a text file, then import into Access.
JimD.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
I take that back...I'm thinking of something else.  dbase files should be an option in the linking dialog.  If not, you didn't install all the Office componets available.  re-run your Office 2000 install.
JimD.
0
 
jschmidt123Author Commented:
There was a copy of Office 2003 basic on this machine.  I uninstalled it and loaded Office 2000 Premium as they needed Access.  After the suggestion to try reinstalling Office 2000, I downloaded the Office 2003 Removal Wizard from Micrsoft and ran it, in the hopes of ensuring that ALL traces of Office were gone.  Then I tried reinstalling Office 2000 and now it gets about 80% of the way through the install and then I get the error messages that says "Unable to access configuration for Microsoft Personal Web Server".  To quote Led Zepplin, I am dazed and confused.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
If you selected "FrontPage Server Extensions" and have the Personal Web Server setup instead of IIS, you'll get that error.
JimD.
0
 
jschmidt123Author Commented:
Thanks.  I went back and uninstalled and reinstalled, but first unchecking the Front Page option for installation.  That did indeed resolve the installation error message so thanks for that.  However, I am still stuck in  my original problem that I posted, namely that I cannot link to a dBase IV table.  Please see my original post.  This has to be something machine specific as I have installed Office 2000 on other machines and can do the linking.  Would appreciate any continued assistance!
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
I remember this being a problem with Access 97 and found the related article:
http://support.microsoft.com/kb/171955
But I don't remember having issues with A2000. There were issues with the Borland Paradox and dBase drivers though because of a law suit. Microsoft released some patches after that, which were included in JET SP 5.0.
I would suggest downloading the latest MDAC drivers from here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en
Then follow the instructions in this MSKB article:
http://support.microsoft.com/kb/271908
and install both the MDAC and JET 8.0 service pack.
Doing that won't hurt anything and if it that doesn't fix the problem, then something is not registered properly.
Let me know...
JimD.
0
 
jschmidt123Author Commented:
I resolved this.  With a little digging between machnes, I discovered that there was no registry entry for msxbde40.dll.  I simply registered the dll  with regsrv32 and it now works.  Thanks all for your valued input!
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<< I simply registered the dll  with regsrv32 and it now works.>>
 That's in the Access 97 article and I thought might be the case ("Doing that won't hurt anything and if it that doesn't fix the problem, then something is not registered properly"), but it never hurts to update everything first.
JimD.
0
 
jschmidt123Author Commented:
I greatly appreciated the quick responses I received, especially considering we were in the middle of the holiday season.  My customer will come in this morning and be ecstatic!  A great way to start the New YEar.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now