This is an issue of Crystal 8.5's API, and VB coding.
We are exploring the possibility of (through software) converting an ODBC report to use Oracle SQL*Net instead, and have encountered something which gives every appearance of being a bug in either the database drivers which are packaged with Crystal, or a bug in Crystal's Report Designer Component (their API).
We are using a custom report viewer built using VB6 and v8.5 of Crystal's RDC uses Report.Database.ConverDatabaseDriver() to convert a report template's connection method from ODBC to Oracle SQL*Net.
After converting the database driver and refreshing the report, data returned from any database columns defined as VARCHAR2 has ".00" appended to the values. This only occurrs when a report is retrieving data from a view or synonym--it does not happen when retrieving data directly from a table.
Searches through Crystal's support site, at best suggests that there is a bug in Crystal's API which is causing this.
There was once a similar issue (table names rather than contents) when upgrading a report developed with CR 6.0 to CR 7.0, for which a software patch was released by Crystal (see link at bottom...if you're interested). We need to establish whether or not the problem we are experiencing now is a bug, whether any patches to Crystal's software are available to rectify this, or if it may be corrected through VB coding.
I know I could "tweak" the data with the REPLACE function, but I would prefer to fix this on the data side rather than having to update each RPT sile to use a formula instead of a field.
If anyone has seen this before, let me know...Thanks in advance.
We are exploring the possibility of (through software) converting an ODBC report to use Oracle SQL*Net instead, and have encountered something which gives every appearance of being a bug in either the database drivers which are packaged with Crystal, or a bug in Crystal's Report Designer Component (their API).
We are using a custom report viewer built using VB6 and v8.5 of Crystal's RDC uses Report.Database.ConverDatabaseDriver() to convert a report template's connection method from ODBC to Oracle SQL*Net.
After converting the database driver and refreshing the report, data returned from any database columns defined as VARCHAR2 has ".00" appended to the values. This only occurrs when a report is retrieving data from a view or synonym--it does not happen when retrieving data directly from a table.
Searches through Crystal's support site, at best suggests that there is a bug in Crystal's API which is causing this.
There was once a similar issue (table names rather than contents) when upgrading a report developed with CR 6.0 to CR 7.0, for which a software patch was released by Crystal (see link at bottom...if you're interested). We need to establish whether or not the problem we are experiencing now is a bug, whether any patches to Crystal's software are available to rectify this, or if it may be corrected through VB coding.
I know I could "tweak" the data with the REPLACE function, but I would prefer to fix this on the data side rather than having to update each RPT sile to use a formula instead of a field.
If anyone has seen this before, let me know...Thanks in advance.