[Pervasive][ODBC Client Interface] Driver unable to load translate DLL

[Guest_imported]

Hi,

I hope that someone can help us out on this. We have searched the Internet from corner to corner, but could not find any solution.

We have installed the Pervasive Client Interface ODBC driver on Windows 2000 and without any problems connected to the database on the remote server. The problem occurred when we made a query to the database with returning field names like &quot;address^1&quot; etc. The ODBC driver stopped us and moaned about the &quot;address<???> ^1&quot; field. We found that the OEM/ANSI Conversion check box on the ODBC setup was not checked. We checked it and tested the connection with the Test button, but the above mentioned error showed up.

Can you please advise us of what the DLL name is that the driver need. Or if it is some other problem that we are not aware of.

Thanks
Jako

 

[mirtheil]

The Translate DLL is W32BTXLT.DLL, if I remember correctly. Unless you know you need the OEM/ANSI translation, you shouldn't check the translation. Usually OEM/ANSI translation is for foreign characters.
Do the fields actually have the carat (^) in them or are they spaces? If the field really has the carat, you'll need to put double quotes around the field name (select &quot;address^1&quot; from &quot;Table&quot. If you were using older ODBC drivers (v2.5x and previous), you might have seen carats as place holders for spaces. If the table has spaces instead of carats, you'll still need to use double quotes (Select &quot;address 1&quot; from &quot;Table&quot. Mirtheil
mirtheil@mirtheil.com
Custom VB and Btrieve development.

 

[Pervasivite]

First, you should check to see if your installation is patched up to SP3 and SP4 level on both the client and the server. You are definitely using Pervasive.SQL 2000, but maybe not the latest version. Then you need to do a consistency check against the database you are tring to query and see what the results are. Next you need to go to the Pervasive Web site and download the CNVDDF utility and doc from the Support Toolbox and read the paper and convert the DDFs if they are SSQL 3 format. You may have DDF problems so try testing a similar query against the DEMODATA database and see what happens. If your test works against DEMODATA but not on your data, then it is likely a DDF or data problem and you would need to fix it or refer the issue to the application vendor.

Regards,
Pervasivite