×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Problems with ODBC and Pervasive 7.0

Problems with ODBC and Pervasive 7.0

Problems with ODBC and Pervasive 7.0

(OP)
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

RE: Problems with ODBC and Pervasive 7.0

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...

RE: Problems with ODBC and Pervasive 7.0

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%.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close