Crystal 8.5 using Oracle 9 - DataTypes change

[Montana751]

I checked Crystal's site and found that Crystal 8.5 is not supported using anything higher than Oracle 8.1. So I am hoping someone can help me figure out what the heck is going on.

Oracle 9 through Oracle 9.02 using ODBC connection.
Have Id fields setup as Numbers (so a 1 shows up as 1.00).
I inserted the database field directly into the detail section of the report. There are only 3 records in the database. The values are 1, 2 & 3 (record ids). When I preview my data, the value that should display as a 1 is showing up as 1111780000. Another instance, have a value that should display as 17.00, but is displaying as 17000

Any clues on what is causing my data to be possessed? If you run a query in Oracle the correct values display. Its only when viewing/querying, etc in Crystal 8.5 that gives this bizarre behavior.

Help!

 

[synapsevampire]

I've used 8.5 against Oracle 9 without this problem, unless you have a data type unsupported by CR.

Perhaps using OLE DB for Oracle will resolve, but I doubt it...

What is the actual data type of the ID field? Oracle doesn't have a *number* that I'm aware of, it does have a numeric.

Try using a SQL Expression to Cast it as another data type, such as a numeric or int, or do so in a View on the Oracle side.

There are other data types that will bite you in Oracle 9, such as the timestamp with timezone. Take the same approach and Cast them either in a View or using a SQL Expression in CR.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[Montana751]

The datatype is number and it has precision and it has always worked until running against an Oracle 9 database that is why I "assumed" Oracle 9 to be the culprit. All kinds of strange behavior is occurring since using Oracle 9 (formula's not displaying data as assigned, this problem with Id's showing up wacky).

I guess I will look into other reason on what would cause my Crystal 8.5 reports to go psycho.

Has anyone else experienced any strange behavior with Oracle 9?

 

[lyanch]

I have had problems mainly with the timestamp datatype. Actually using ODBC with the datatypes causes crystal to crash. When I changed to the native driver that problem went away. I do however have to convert it to a datetime before Crystal can "see" what the value is.

Lisa

 

[Montana751]

Found the culprint; P20DBC.dll version 8.6+ causes data to display differently then expected. For example I have a Number field which SHOULD display as 1.00, but displays as 49 or 5178000 or 98273490. (I only have 2 items in the database, item 1 and item 2)

When I removed this DLL and used version 8.5.0.72, the value appeared as it should. This DLL is found in the System32 folder.

Wish me luck, I'm going to attempt to find out from Crystal what the problem is with this DLL.