Import Paradox 7.x table to Sql Server table using SSIS

  • I am trying to import paradox 7.x table to sql server using SSIS. Can anyone help how to configure the connection string. I am getting error saying Invalid path name and i am assuming that is because it doesnt recognize the *.DB extension. When i try to use the odbc connection it provides it only upto Paradox 5.x version. I use the same tables to connect it to excel using MS Jet OLEDB provider it works fine, when i try to use the properties in connection manager in SSIS package it doesnt work. Can anyone help me on this?

    Thank you,

    Ashu

  • Hi,

    Run into this problem recently when trying to import Paradox 5.x files to SQL Server 2008 R2 via SSIS in Windows 7.

    What was missing?

    - The Borland Database Engine (BDE). I have installed the 5.2.0.2 version downloaded at http://www.prestwood.com. You need to register into the site in order to get it. This is the name of the downloaded zip file "mprestwood_KB100537_attachment.zip".

    So, after installing the BDE, solved the problem with these steps (witch i think all of you should already have tried with no success):

    - Create a System DSN with the Paradox Driver, using ODBC 32 bit Manager, usualy at <drive>:\Windows\SysWOW64\odbcad32.exe, configuring it to point to the folder where the paradox .DB files are.

    - In SSIS, create an ADO.Net connection manager using the previous created DSN

    - Configure the created connection manager to use the provider ".Net Providers\Odbc Data Provider", and in the Data source specification select the created system dsn

    - In a Data Flow Task, add an ADO Net Source using the created connection manager

    "Automagicaly" everything goes as it should, you can see the paradox files appearing as tables, their columns, etc. Now you only have to choose your destination...

    Hope this helps, i sure wasted a great deal of time to get this running... but is running, time to move on...

    JB

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply