Everyone,

I did a search for CLOB on FocalPoint and found some discussions dated back to 2004 which did not seem to hit what I need.

We have Oracle 9.2 with a database that contains CLOBs. Most records can be handled with an A2000 but there are some records that have a value in the CLOB of over 20,000 characters. Does anyone have a good way to handle these? Have any new features/commands/enhancements been added to WF713/714/76 to handle these monsters?

Just to clarify, I do not want to use TXnn for these fields. There are too many limitations on TXnn fields. I want to treat the CLOBs as Annnnn[V] if possible.

Mickey
we had a question like this on a BLOB and the answer was it would be solved in 7.6....so may be it also works for CLOB's

Frank,

I'll take a look at the "Sum of New Feats" for WF76 to see if there is anything in there.

Frank,

I pulled up the WF76 SNF and did a word search for CLOB and BLOB. It did not find either of them.

I will dig more on Monday.

To those who are interested,

In WF713 I found that using a TX250 got me down the road of getting ALL the contents of a CLOB from an Oracle database field. This was the only format that would pull the complete contents of the CLOB over to WF without causing other issues or bumping into limits. Ironically declaring a CLOB as a TX field respects the carriage returns in the CLOB and created fairly nice output consistant with the actual format of the text in the CLOB.

There are limitations on what you can do with a TX field but this ended up being my only solution.

AnVs happily go up to 8000 even tho docs say 4k - this not applies to An s

hammo1j,

The CLOB can go to more than 32,000 characters which is way bigger than an A8000V. We have some records with over 20,000 characters in the CLOB. This is what was causing me issues. I was able to create an A30000 (30,000) field and use it but had to limit the number of fields in the request due to limitations of the total length of all fields in a request. Therefore, TX was my best option.