thread766-998445 We have been ab

[PhilB2]

thread766-998445

We have been able to read the first 3820 characters of a clob field using the SQL view statement below, to avoid the clob data type error and also a buffer error (when we used 4000 characters). This allows us to run a Crystal report and an application called DARTS. However, for the Crystal Report we occasionally need more data than just the first 3820 characters. Any suggestions, please?

, dbms_lob.substr(badgir.ts_ti_promote,3820,1) "Technical_Instructions_Promote

 

[Turkbear]

Can you use more than 1 dbms_lob.substr with a offset starting at the end of the previous one and concatenate the results ( or just place each of them next to each other in the report)?



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

 

[PhilB2]

Thanks, I had gotten that solution working before I read your post.

In order to avoid splitting lines in the report, I had tried to group all 8 4000-character columnns into one field in the report, but the report could only handle 3 at a time (otherwise, no data displayed). I don't think anyone will actually submit a field with more than 12000 characters, but if so, a line will likely be split, and that's an acceptable compromise in this case. So I have 3 separate detail sections, with 3, 3 and 2 fields concatenated in the 3 sections, respectively.

Another problem was that before if a user linenumbered his/her data in the CLOB field, multi-byte characters were introduced that Crystal couldn't handle, displaying a buffer error. Unchecking the distinct data option didn't seem practical, but a developer provided the following substitution in the view, and that avoided the buffer error:

, dbms_lob.substr(replace(badgir.ts_ti_promote, NCHR (160), ' '),4000,1) "Technical_Instructions_Promote