Frustrated with Pervasive/Crystal Reports 2

[DonMc67]

Hello,

I've been accessing various Btrieve/Pervasive dbs with Crystal Reports. I typically have been connecting natively. In order to cut down on processing time I've started to connect to an ODBC DSN for the data I used to connect to natively and then using the Crystal SQL designer. This way is MUCH faster, but there is a major problem and both companies are blaming each other.
PROBLEM:
There are several fields that are usmallint (0-65,xxx) these are reported fine through the native connection, they are reported fine connecting ODBC through SQLCON32, but when they are connected through the ODBC DSN onto the report they are displaying smallint values (-32xxx to 32xxx)

Both companies admit there's a problem, and both blame each other... anyone know anything more about this??

 

[Pervasivite]

The problem may be in the metadata which is contained in the DDFs. Exactly which versions of Pervasive and Crystal do you have? To check to see if it is a problem in Pervasive or in Crystal test the Billing Table in the Demodata which has a usmallint in it. If that displays incorrectly it is probably a problem in the Pervasive engine. If you are not on Pervasive.SQL 2000i (SP3) or Pervasive.SQL 7 SP5 then you should apply the latest service pack and see if that helps. If the field displays correctly in Demodata then it is either a problem with the metadata (you can compare how the data is entered in the DDF in Demodata vs. how it is in your production data) or it is an issue with Crystal. Do you have any incidents entered with Pervasive Support and if so what is the incident number?

Pervasivite

 

[DonMc67]

I am running i and Crystal Reports 8.5. I ran this on the Demodata.class using the max size field. Changed some records to >32767 and then created a Crystal Report with just that field. The report returned the records I changed as negative values.

My incident number :A10630477
I've been working with Michael Beris

 

[grnelson]

I've used Crystal reports since version 4 with Btrieve and have over the years written over 100 reports and it's always been a great tool except for a few things that you could work around. I recently purchased version 8 and I could never even get it to work and after spending a few days on it gave it up. I went back to using version 6 but will eventually migrate off of it entirely. Version 6 had a problem of always sending reports to tray 1 which was the reason for moving to version 8 but at least 6 worked well.
Gil Gil

 

[EricdlH]

Excuse my inexperience, I am new to both Pervasive and Crystal. I inherited 200 ver 8.5 reports running off the Pervasive ODBC and it appears that the SQL FROM clause, as generated by Crystal, is back-to-front as far as Pervasive ODBC is concerned and the result can hang the server. I would really appreciate any ideas.

Eric