Link to home
Start Free TrialLog in
Avatar of Tom Crist
Tom Crist

asked on

Trouble Linking dBase Files to Access 2010

Hello,

Here is the  background on the  problem we are  experiencing:

- We have switched from MS Access 2007 to MS Access 2010.  Since then we have had problems linking dBase files into Access 2010.  We can browse the files in Access 2010 but when we select the file, we get the error message that the file can not be found.  We can log off the machine and log back on and it then works......temporarily.  Then we start getting the same can not find file  error message.

Please note the dBase files names are longer than 8.3 naming convention....These files were produced in a third party software application.....We do not have the problem with linking these  same files in 2007 only Access 2010.

I looked through prior questions that were similar in nature....It appears that a Visual FoxPro driver might be the answer....However,  I can't download the driver "vfpodbc.msi" because it is no longer supported.

Please help me, Obi-Wan Kenobi; you're my only hope.

Thanking You In Advance
T. W.

 

Avatar of Richard Daneke
Richard Daneke
Flag of United States of America image

You may benefit from running the Microsoft 2003 Conversion Toolkit to check on connection issues.  It is free and available here:
http://office.microsoft.com/en-us/office-2003-resource-kit/microsoft-office-access-2003-conversion-toolkit-HA001140166.aspx
Let us know if this helped.
ASKER CERTIFIED SOLUTION
Avatar of Tom Crist
Tom Crist

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
To use filenames in 8.3 format helps obviously to dBase driver (even in the 64 bit environment)...

Why you cannot download the VFP ODBC driver? It is still available here: http://msdn.microsoft.com/en-us/vfoxpro/bb190233  BUT it does not work in 64 bit Access.
We have been trying to help but you are ignoring our answers...

And while you were waiting Microsoft moved the ODBC driver to another location...

OK, close this question.
Avatar of Tom Crist
Tom Crist

ASKER

No reason...