Giving All Permissions to Everyone under applications' folder, under databasefolder, under registry folder HKEY_LOCAL_MACHINE\SOFTWARE\ODBC as described here , under odbc* files in %WINDIR%\System32 does not help.
DataDirect provides this Paradox 7.x table format driver with read-write capability. Note that Paradox tables remain frozen at table format 7.x, That means that software mentioning Paradox 8, 9, 10 tables are really always referencing format 7.x.
I got a Problem with an old ODBC Driver for Paradox Database (Intersolv ODBC Paradox Driver). I have an application to read and write data to a Paradox database while the Main Program of the Databases is running. I have got Problems before with the MS Paradox Driver. Now with this driver everything works fine and I can work simultaneously on the Database. My Problem is this only works with Windows 10. With Win7 I get an Error when trying to open the Database (SQLAllocHandle error). If I close the Main Program the driver works. I tried to access the Database with a Windows Service and that works on Win7 I can access the Data while the Main Program is open.
I was having this exact same problem on a 64 bit system, trying to open a Paradox table to read data while the original Delphi application also was running. Using the Microsoft Paradox driver I would get the "External table is not in expected format" error when I tried to execute my ODBC DataReader, and if I used the Intersolv driver, it would give the same SQLAllocHandle error that you are seeing when I tried to open the connection.
Is it possible to install and where do I obtain the Microsoft ODBC Paradoc Driver for Windows 7? I can't seem to locate it in the ODBC Datasources Administrator like I could in WinXP and Vista on the drivers Tab.
You are right, you have pointed to ODBC Addministrator tool, but- at least for 64-bit version of Windows 7 - the problem remains. There are no Paradox drivers. So, where do we obtain the Microsoft ODBC Paradoc Driver for Windows 7?
The following table shows the minimum keywords required to connect to each driver, and provides an example of keyword/value pairs used with SQLDriverConnect. For a full list of DRIVERID values, see SQLConfigDataSource.
This dialect is mainly intended to offer an easy way to access theParadox DB flat-file databases of older or EOL'd application-specificsoftwares. It is designed for use with the ODBC driver included withmost versions of Microsoft Windows, Microsoft Paradox Driver (*.db) ODBCJT32.DLL.
It is generally a good idea to download and install both the 32-bit and 64-bit MSI packages. Otherwise, the ODBC Driver Manager may sometimes load the wrong version of the driver for your application, which can cause errors like the following:
The installation process is fairly easy. First, you need to extract the files from the binary tarball. Then, you need to install the driver's shared library to the appropriate place in your system. The driver's shared library is called libmaodbc.so and it is located in either the lib directory or the lib64 directory, depending on whether you downloaded a 32-bit or 64-bit package. The driver's shared library can be installed anywhere, but for simplicity, the instructions below will assume that you are installing it to /usr/lib64, which is a common directory for 64-bit shared libraries on many Linux distributions.
Devart ODBC Drivers are powerful connectors for a host of database management systems and cloud services that allow you to connect to your data from virtually any third-party application or programming language that supports the ODBC API. By a third-party application, we mean tools like Power BI, Tableau, Microsoft Excel, etc. See this page for the list of external applications that have been tested for compatibility with our drivers.
Before connecting a third-party application to a database or cloud source through ODBC, you need to set up a data source name (DSN) for the ODBC driver in the Data Source Administrator. A 64-bit version of the Microsoft Windows operating system includes both the 64-bit and 32-bit versions of the Open Database Connectivity (ODBC) Data Source Administrator tool (odbcad32.exe):
Yet another way to open the ODBC Data Source Administrator is via the command prompt: enter cmd in the search bar and click the resulting Command Prompt button. Enter the command odbcad32 and hit Enter.
4. Enter a name for your data source in the corresponding field. Fill in the parameters for the ODBC connection string, which is driver-specific. In most of our ODBC drivers for databases, a connection string with basic parameters requires the user to only input their server address, port number, and login credentials, since Devart ODBC drivers allow direct access to the database without involving additional client libraries.
The steps for configuring an ODBC DSN for a 32-bit driver are practically the same as for the 64-bit driver, except for the step where you select the 32-bit version of the ODBC Data Source Administrator. Running the odbcad32 command in the Command Prompt or in the Run dialog box will start the 64-bit version of the ODBC administrator on the 64-bit Windows by default, therefore your best option is to select the 32-bit version of the administrator in the search results of the Windows search box.
Note though that if you have both versions (32-bit and 64-bit) of the driver installed and you have configured a User DSN (in contrast to a System DSN), you will be able to use the same DSN for 32-bit and 64-bit applications (see the Platform column in the screenshot below).
In a situation where you need to use an application that is available only in 32-bit, the 32-bit ODBC driver does the trick. An example is Apache OpenOffice, which is distributed as a 32-bit application.
I do not see the Paradox drivers however from the odbc icon inPowerBuilder. I supposed I needed to go into control panel and makeuse of the 32 bit odbc option (icon). When I select add, I do seereference to the the Paradox driver in the list, but when I select itI get the following:"The setup routine for the PB Intersolve 2.12 32 Paradox file ODBCdriver could not be loaded due to system error code 1157". Then I geta dialog saying "Could not load the setup or translator library"I am correct in assuming that the Paradox driver is available in PBdesktop, arn't I. Can someone tell me what is going on and what I need to do to be ableto acces Paradox tables for use with the Pipeline?Woody Splawn
To fix: you need to add (*.db) after the Paradox driver entries inthe ODBCINST.INI file/registry setting as well as in the ODBC.INIfile/registry (although you may not have anything there yet). The Paradoxentry should read something likePB Intersolv 2.12 32-Bit Paradox Driver (*.db) whereas now it probablydoesn't have the (*.db) on it.The problem you are getting in ODBC Administrator usually indicates apathing issue. You need to make sure the all the DLLs needed for thedriver can be found in the path (they have names like PBxxx09.DLL and arelisted in Appendix B of the User's Guide) . Additionally, check forPBFLT09.DLL - this DLL is necessary and didn't make it on some of the CDinstallations. If you find you do not have this DLL and it's not on theCD, 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 youwere to get the 5.0.03 maintenance release from the Web site, I believeyou would be all set.Jim O'NeilPowersoft Technical Supportjon...@sybase.com
Thank you for responding. With regard to PBFLt09.dll, I do have this file, its in my WindowsSystem dir. I have added the Windows\System dir, explicitly to my pathstatement in Autoexec.batAs you know, unless everything is exactly the way the computer wantsit, things sometimes just won't work. I would very much appreciate aprint out of an odbc.ini and odbcinst.ini file where things are typedin correctly. There are several places in mine where Paradox can orshould be mentioned. I might get it right in one area, but skip aspace or something in another and waste a great deal of time trying tofigure out what it wants.I do have PB 6.0 and I re-installed it (after your message) with theParadox drivers, thinking it might make the changes for me in the inifiles. However, I still have the same problem. I need to knowexactly ( if you will) what needs to be typed in the specific sectionsof the files. I suppose that is what is needed and that I do not need to go into theregistry, right? I must admit, I do not understand the registry verywell. All the DLLS that are needed do seem to be on my system.
>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 (*.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. 2b1af7f3a8