There are only two ODBC drivers for Btrieve v6.15. One was from Intersolv and one was from Pervasive. As far as I know, neither are available.

If you can, upgrade to PSQL v11 (the current version of Btrieve) and it includes an ODBC driver.

You will need an engine on the same machine as the Btrieve data files. There is no way to access the data files without an engine.

Hello,

How can I tell from my system which PSQL version we are using.

Is it a lot of work to move the system up to PSQL11??

It seems I have an uphill struggle on my hands :-

1) upgrade PSQL
2) install PSQL on client PC
3) create ODBC DSN's to the .btr and .ddf files
4) figure out how to use both to get a workable set of tables in Access or SQL Server

Is that about right?

Thanks
Phil

The easiest way to find out what version you are using is to look for any of the following files and look at the "Verstion" information in the Properties of the file. The files are:
W3BTRV7.DLL
WBTRV32.DLL
W3DBSMGR.EXE
W3ODBCEI.DLL
W3ODBCCI.DLL
W32BTINT.DLL
W32MKDE.EXE

Moving to PSQL v11 may not be a lot of work. It depends on your application. For example, if you application is 16 bit, it won't work because v11 dropped support for 16 bit applications. If your application is hard coded to look for a specific version of Btrieve, it may not work as v11 reports its version as 11.00. Best thing I can suggest would be to install v11 on a test system and run your application.
You’ve got the basic steps down:
1. Install PSQL / Btrieve on the client / server.
2. Create the ODBC DSN pointing to the DDF/ data files.
3. Link the table in Access or create a Linked Server in SQL Server.

Now, how you do these is up to you. PSQL v11 is the most current version of Pervasive / Btrieve. It’s available as a workgroup engine, server engine on Windows (32 bit and 64 bit) and Linux (32 bit). You should choose the one that’s going to fit your needs. For example, if you are only going to access the data one time and it’s all going to be on one system, the Workgroup engine might work best.
Once you get the PSQL engine installed, you would create the ODBC DSN using the ODBC Data Sources applet or you can create the DSN using the Pervasive Control Center (documented at http://docs.pervasive.com/products/d...3.1.html#89434).
Once you’ve got the DSN created, you can link the table through Access using “Get External Data” or you can create a Linked Server in SQL Server (sp_addlinkedserver (Transact-SQL)).

Hi!!

A little success!. I installed Pervasive on the client and with it have two ODBC drivers :-

1) Pervasive ODBC Client Interface
2) Pervasive ODBC Engine Interface

I have played around with both but have been unable to connect to the ddf files.

Using the Engine Interface I input a Data Source Name i.e. TestConn

Under Database I click 'Create' give it a made up database name i.e. TestConn and Browse to the Dictionary location where the ddf files are. This also adds the same location to the 'Data File Location' box which is OK as the btr files are there also. When I press 'Test' I get an error :-

[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface][Data Record Manager]The Btrieve file directory is invalid(Btrieve Error 35)

I feel I have moved forward!!

Can anyone help with the above.

Also just to test my ODBC connection is there a way I can copy the File.DDF to MyDocuments and then just connect MS Access to that just to test reading the ddf file using ODBC???

Thanks
P

Did you install the PSQL client or Workgroup or Server engine?

When you browse to the directory where the DDFs / Data files are located, are you browsing to a remote directory or a local directory?
If it's remote, are you using mapped drive or UNC (\\server\sharename)?
If you installed the Workgroup, did you install it as an application or service?

Unfortunately, the DDFs are a set and you can't copy just the FILE.DDF and open it up. To use ODBC in Access, you have to create a DSN that points to the database name that points to the DDFs and data files.

Hello,

I found I was able to create an ODBC DSN to the DEMODATA ddf and data.

I then cleared this folder out and copied the DDF's into this folder. I could then create the DSN and in Access when I clicked the data source it brought up a list of tables from the database I am trying to connect to.

This felt like some success

However it wouldnt let me import or link to any of the tables.

I thne opened the file.ddf in notepad and noticed that the location of the .btr files is a slightly different one to the location to where the ddf's are

They are both remote locations to mapped folders

When I installed PSQL I installed the Client Tools, and it comes up in my Start-All Programs list

I tried to set up a DSN using the foler name of the btr files as the database name, browsing to the path where the ddf's are and in the data file location brwosed to the location referred to in file.ddf, but with no joy (get the same error as before)

I feel I am on the precipice of success!!!

Cheers for your help
P

Hi,

I feel that it is the name of the database I am getting wrong when I am trying to connect to the remote ddf's and btr files.

Is there a way (if the person who installed the database left many years ago) to find the name of the database i.e. from the ddf files or any other tool/method

Thanks
P