Invalid characters in DB -Please help

[PENGY]

I am working on a report using a DB with a fields that I cannot change.

I am querying a Oracle DB field that when filled by the program places characters in the fields that cause crystal report to stop reading (whatI call invalid). The field is some type of extended memo that has a max of 1300 characters (or lot anyways)

When I try to display this field currently in my report the data gets cut off at the first of these invalid characters

(I am sure that that all the data available is not displayed)

I am looking for a procedure in the report to allow me while reading the field replace any non A-Z,a-Z,0-9 characters with a space and allow the entire data string to be displayed.

Any ideas?

 

[Turkbear]

Hi,
I would suspect a CR or CR/LF character has gotten in there..

To determine the best way around this we need the version of Oracle and the connection method.
Perhaps using a Sql Function to read the data and do a replace.

What do you see if you query the data directly ( like with SqlPLus )?







To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[synapsevampire]

Please post technical information:

Crystal version
Oracle version/connectivity used

A common problem along these lines is to use the Oracle supplied ODBC driver, instead of the one supplied by Crystal, or better yet, using native connectivity.

If you do have extended ASCII that is throwing errors, you might create a SQL Expression to remove them, but we'll need more info.

Try the first suggestion, that's a common problem.

-k

 

[PENGY]

crystal version 8.5

I log on to the DB through a source I configured under my ODBC administrator that looks at a the connection I set up using Oracle SQL Easyconfig

On the ODBC admin the source says it is using CR Oracle 7 Driver version 3.50.00.00 by MerantINC (hope thatthis helps)


I am pretty sure it it a CR/LF character causing the grief.

 

[synapsevampire]

Select format field and turn on the can grow. A CR/LF doesn't mess Crystal up, it just does as it's told.

Use the Oracle native connectivity for better performance (Select Oracle Server as the source, you can use Database->Change Datasource location for this).

-k

 

[PENGY]

Can grow does not work.
I have tried oracle native connectivity results are the same.

The field is a Varchar2 (608) type.

Using SQL to view the info I realized there are a lot more nonprintable characters in the field than I thought.

Is there a way to allow me while reading the field replace any non-printable characters with a space/or dash before sending it to the report.