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?
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?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!
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!
That's encouraging. Normally patches seem to cause me problems rather than fix them! :-) Good luck.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Another option is Visual FoxPro ODBC driver: http://msdn.microsoft.com/en-us/vfoxpro/bb190233.aspx