Problems with ODBC and Pervasive 7.0

[harcoj]

Hi All,

As an inexperienced Pervasive user, I have started experiencing an intermitent problem when using ODBC to connect to a Pervasive 7.0 database. The specific problem seems to be related to the way the ODBC driver is interpreting index data. In effect, instead of returning a series of fields per table, the same two field names are being returned for each field in the table.(This then gets rejected by Access or whatever you are connecting to)

It subsequently came to light that the two repeated fields were those used in indices on the tables trying to be accessed. No errors were returned either from Btrieve or through the ODBC driver and we just got junk data when using SQL Server DTS / Crystal Reports. This behaviour lasted for a week and then mysteriously disappeared. I'm very nervous that it may return again.

Has anyone experienced something similar? I am very new to Pervasive so any ideas / advice would be appreciated.

Many Thanks

 

[TomKane]

I found a problem with Pervasive SQL when I tried to use a query such as the following:

SELECT CustCode as Customer_Code, CustName as Customer_Name FROM Customer WHERE CustCode > 100 ORDER BY CustName

That's not the exact query but the problem was that it didn't use the aliases unless I took the ORDER BY away. I think sometimes that you have to compromise your queries to get them to work properly. I had to do a bit of a work around in the end.

I suppose what I'm saying is that it could be that something you did fixed it but it's not obvious what. Try to think about what steps you took to try to fix the problem - one of them could have been the one...

 

[vbajock]

I've had similiar problems. It seems to be on ver 7 only - It always seems to happen when I am using a frontend that uses has a different version of SQL than the ANSI sql used by Pervasive - there are bugs in the translation of some of the statements. Upgrading to 2000i solved my problems with this about 99%.