Error in importing dbf to Access 2007 / Excel 2007

I have come across a problem with importing / linking dbf files as datasources into Access or Excel 2007 that has something to do with a version difference.

Here is the scenario:

New workstation configured from scratch with Win XP SP3 and Office 2007 Pro SP 2.  All security updates and patches installed.  Attempt to import a valid (and uncorrupted) dbf into a new table and receive the error message:  "The Microsoft Office Access database engine could not find the object 'xzyfilename'. Make sure the object exists and that you spell its name and the path name correctly.  (Receive the same error when trying to link it as an external data source in Excel - I have also tried this on a Vista system with the same problem)

Old workstation with Win XP upgraged to SP3, originally office 2003, upgraded to 2007 with all SP and patches installed.  Importing the same file works as expected without any issues.

I've been pulling out what little hair I have left trying to identify a difference between these systems that is causing this.  I was thinking it had something to do with a difference in the OLE DB drivers, but those versions seem to be the same. Any advice or suggestions on what I should be looking for?

Stan_GAsked:
Who is Participating?
 
Stan_GConnect With a Mentor Author Commented:
So not exactly sure what winds up getting changed, because all the ADO / OLE driver versions are still the same, but installing the Access 2007 Runtime (and associated updates) over the full version of Office 2007 Pro and then retrying the same files everything works as they did before.
Thanks for the info....
0
 
OxonDevConnect With a Mentor Commented:
I does look like a driver problem.  I reckon you'll have two verions on the old pc and only one on the new.  If that's the case new driver will be ignored on the old machine, and the old driver will be missing on the new machine.  

You can check if the new drivers would ever connect to the DBase file by attempting to create an ADO connection in code.

Other things to look for would be are file paths UNC or mapped...  If a drive isn't mapped, or isn't mapped with the same letter it'll be entertaining.
0
 
pcelbaCommented:
Access driver does not recognize long filenames when reading DBF files. You should try the filename in 8.3 MS-DOS format and you'll see.

Another option is Visual FoxPro ODBC driver: http://msdn.microsoft.com/en-us/vfoxpro/bb190233.aspx
0
 
Stan_GAuthor Commented:
OxonDev - I'm waiting to have access to the workstation in question once more, but I found that installing the Access 2007 Runtime and associated patches on the Vista workstation seems to have alleviated the problem on that particular machine - just need to try it on the other one.
pcelba - 8.3 is definately not the issue - as the same file worked on another machine (even though that was one of the first things I checked).  
I will post another update in the next day or two once I can get to the other workstation.
Thanks!
0
 
OxonDevCommented:
That's encouraging.  Normally patches seem to cause me problems rather than fix them! :-)  Good luck.
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.

All Courses

From novice to tech pro — start learning today.