×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

thread766-998445 We have been ab

thread766-998445 We have been ab

thread766-998445 We have been ab

(OP)
thread766-998445: CLOB data types in CR 9 / 10

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"

RE: thread766-998445 We have been ab

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)?

profile

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

RE: thread766-998445 We have been ab

(OP)
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"

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close