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

SQL 2008 64Bit and dBASE III Application

All, I am trying to link my SQL 2008 64bit server to a legacy dBase III program that we have on site using the linked servers in SQL.    After much reading on the internet and trial and error I have downloaded the ACE 64bit driver and I am using the following query:

EXEC sp_addlinkedserver @server = N'WINTAM', 
@srvproduct=N'DBF', @provider=N'Microsoft.ACE.OLEDB.12.0', 
@provstr=N'DBASE IV' ;

Open in new window

This completes however when I go to test the connection I get an error that says the @datasrc is not a valid path.    I know the path is correct so it must be something different.

Currently I am using a SSIS job to upload information from this database hourly but I want to be able to update it in real-time so any other suggestions on how to do this are also welcome.
Earl Kelly
Earl Kelly
1 Solution
Chris LuttrellSenior Database ArchitectCommented:
Check the service account you have Integration Services running as and make sure it has access to the source path.  It sounds like a possible permission problem to me.
Even the 64 bit ACE.OLEDB driver does not recognize long path names...

You have to define the datasrc by 8.3 notation only:   d:\folder1\subfldr\

To obtain 8.3 names of your folders you may issue  DIR /x  in CMD window.
Earl KellyAuthor Commented:
So the syntax is correct?     I tried both AND get the same this same error:  Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "WINTAM".
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "WINTAM" returned message "'\\server1\sharefolder\tam' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.". (.Net SqlClient Data Provider)

In your example above, you stated a drive connection.   I tried that as well and got the same message.   and where does the drive need to be connected on the sql server itself?
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

8.3 path name does not include UNC pathes.

You should really test the format   d:\folder1\subfldr\   where "d:" represents one single disk drive letter.

To access DBF files on another computer is a little bit problematic task...

It means you have to place DBF files on the same computer where is the SQL Server Service running. The drive letter is C: or D: (etc.) then. The user under which is the SQL Server Service running must have full access to the folder where you placed DBF files and the folder name must be in 8.3 format in connection string.
Kalpesh ChhatralaSoftware ConsultantCommented:
Kalpesh, did you already use the Sybase 64 bit driver to read DBF tables from SQL Server?
Earl KellyAuthor Commented:
I couldn't get this to work.   I ended up creating a 32bit server and working from there.
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

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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