How install Paradox odbc driver
Woody Splawn
I have been trying without success to install the Paradox odbc
drivers. When I installed PowerBuilder, some other odbc drivers got
installed ok. For example, I have the Microsoft dbase driver and the
PB Intersolve betrieve driver. I have several others too. That I can
see when I click the configure odbc icon in Powerbuilder. I am using
PB 5.02. Desktop. I did a reinstall today and I did check the Paradox
drivers option.
I do not see the Paradox drivers however from the odbc icon in
PowerBuilder. I supposed I needed to go into control panel and make
use of the 32 bit odbc option (icon). When I select add, I do see
reference to the the Paradox driver in the list, but when I select it
I get the following:
"The setup routine for the PB Intersolve 2.12 32 Paradox file ODBC
driver could not be loaded due to system error code 1157". Then I get
a dialog saying "Could not load the setup or translator library"
I am correct in assuming that the Paradox driver is available in PB
desktop, arn't I.
Can someone tell me what is going on and what I need to do to be able
to acces Paradox tables for use with the Pipeline?
Woody Splawn
Jim O'Neil [Powersoft]
Depending on what version of PowerBuilder Desktop you have, you may have
run into an installation bug. PowerBuilder Desktop will only work with
the drivers shipped with the product and looks for specific strings in the
ODBCINST.INI and ODBC.INI files. Unfortunately, when the Paradox and
DBase drivers were installed by PowerBuilder the these descriptive strings
did not match.
To fix: you need to add <space>(*.db) after the Paradox driver entries in
the ODBCINST.INI file/registry setting as well as in the ODBC.INI
file/registry (although you may not have anything there yet). The Paradox
entry should read something like
PB Intersolv 2.12 32-Bit Paradox Driver (*.db) whereas now it probably
doesn't have the (*.db) on it.
The problem you are getting in ODBC Administrator usually indicates a
pathing issue. You need to make sure the all the DLLs needed for the
driver can be found in the path (they have names like PBxxx09.DLL and are
listed in Appendix B of the User's Guide) . Additionally, check for
PBFLT09.DLL - this DLL is necessary and didn't make it on some of the CD
installations. If you find you do not have this DLL and it's not on the
CD, then call tech support and someone will send it to you.
These problems all occurred with 5.0.01 and 5.0.02 (I think?), but if you
were to get the 5.0.03 maintenance release from the Web site, I believe
you would be all set.
Jim O'Neil
Powersoft Technical Support
jon...@sybase.com
Woody Splawn
Jim,
Thank you for responding.
With regard to PBFLt09.dll, I do have this file, its in my Windows
System dir. I have added the Windows\System dir, explicitly to my path
statement in Autoexec.bat
As you know, unless everything is exactly the way the computer wants
it, things sometimes just won't work. I would very much appreciate a
print out of an odbc.ini and odbcinst.ini file where things are typed
in correctly. There are several places in mine where Paradox can or
should be mentioned. I might get it right in one area, but skip a
space or something in another and waste a great deal of time trying to
figure out what it wants.
I do have PB 6.0 and I re-installed it (after your message) with the
Paradox drivers, thinking it might make the changes for me in the ini
files. However, I still have the same problem. I need to know
exactly ( if you will) what needs to be typed in the specific sections
of the files.
I suppose that is what is needed and that I do not need to go into the
registry, right? I must admit, I do not understand the registry very
well. All the DLLS that are needed do seem to be on my system.
On Wed, 21 Jan 1998 08:28:38 -0500, "Jim O'Neil [Powersoft]"
<jon...@powersoft.com> wrote:
>Depending on what version of PowerBuilder Desktop you have, you may have
>run into an installation bug. PowerBuilder Desktop will only work with
>the drivers shipped with the product and looks for specific strings in the
>ODBCINST.INI and ODBC.INI files. Unfortunately, when the Paradox and
>DBase drivers were installed by PowerBuilder the these descriptive strings
>did not match.
>
>To fix: you need to add <space>(*.db) after the Paradox driver entries in
>the ODBCINST.INI file/registry setting as well as in the ODBC.INI
>file/registry (although you may not have anything there yet). The Paradox
>entry should read something like
>PB Intersolv 2.12 32-Bit Paradox Driver (*.db) whereas now it probably
>doesn't have the (*.db) on it.
>
>The problem you are getting in ODBC Administrator usually indicates a
>pathing issue. You need to make sure the all the DLLs needed for the
>driver can be found in the path (they have names like PBxxx09.DLL and are
>listed in Appendix B of the User's Guide) . Additionally, check for
>PBFLT09.DLL - this DLL is necessary and didn't make it on some of the CD
>installations. If you find you do not have this DLL and it's not on the
>CD, then call tech support and someone will send it to you.
>
>These problems all occurred with 5.0.01 and 5.0.02 (I think?), but if you
>were to get the 5.0.03 maintenance release from the Web site, I believe
>you would be all set.
Woody Splawn
Woody Splawn
Marvin Young
I also had problems getting the Intersolv drivers to work from PB
Enterprise 5.0.02. I eventually ended up using the Microsoft Paradox
driver included with the ODBC 3.0 SDK, which I downloaded from
Microsoft. Alhough I haven't really tested in production, I seem to be
able to use pipelines in development pretty reliably.